Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BCrawlabilityno robots.txt, no sitemapREVIEW
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.
Learn more ▾ ▴
A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.
Source: robotstxt.org
A sitemap helps search engines discover and index your pages more efficiently.
No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.
Learn more ▾ ▴
A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.
Source: sitemaps.org / Google Search Central
No robots.txt found
This is fine for most sites — a missing robots.txt allows all crawling by default.
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations131 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- Enable DNSSEC on your domain for DNS spoofing protection
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+DNS Records2 A records, 95 ms lookupPASS
| A | 16.54.79.180, 15.157.20.58 |
| AAAA | — |
| CNAME | — |
| NS | ns0.dnsmadeeasy.com, ns4.dnsmadeeasy.com, ns1.dnsmadeeasy.com, ns2.dnsmadeeasy.com, ns3.dnsmadeeasy.com |
| MX | 5 mx2.fourseasons.iphmx.com 5 mx1.fourseasons.iphmx.com |
| TXT | apple-domain-verification=bpjOwKJ1Iian7S27 adobe-idp-site-verification=82f13999f4bd23401be04dc020484b6b5294d76fc1bfe0e73ff0... ca4b6f3128ad45acb4581a6375805e57 3S9xVZ2maG/G70TOQ3eeLVMfePEdwMORNYY8BevCzGPUHKh5dodHrJO0f/UCtFWVDfxh5cBuy5ljbIS7... apple-domain-verification=pvgjAJBTWjaKsJEt facebook-domain-verification=kaqyycsdl7otaidlefbjlh2pr3kxan facebook-domain-verification=livazhuusfsdji0sn20o2isvx9zeia p1li98o8o5mnb9hbt0ic2f9j86 google-site-verification=mI4f9gUMfSrHrBya6_d2JQf6rZmCvBPuDZ_dVS9oUdc onetrust-domain-verification=13714331c4d149b6a2dae97c2b1b77b8 SFMC-T2ZUjByUWGduy6BwUd0YrPBeQsUyrPYZ4fom6k9K _globalsign-domain-verification=Um1ppI9F7FGTst3i-geBgfunTCYGkiTcWHi9ZB3CeS apple-domain-verification=PIDkZIrI8N4r0frn _gpxqifp5bfgl0habclfkk10oeem6z24 _11x6w480opgf0374fwo4oq2b2649h9n _globalsign-domain-verification=4hUC-wvfCqObqLqyTqZAVeyVGq017edZUBBTN3E7f9 atlassian-domain-verification=Cmcz1rQ4MvnyqbkT8LKT0lScPxmWLdvpth5jaLHElz56LpwCfG... SFMC-8TvFeym_f5h3fnkHvQcV8B-PhhYhDHPRhz2f71Zb _globalsign-domain-verification=GkgYM8f6ij9jVD7aZ0HzuzQsAnLdkBQCj__k_gBmzu SPF v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all _globalsign-domain-verification=YlUWHil3iMvsxWaA_EVjwaz28dKrdCiKKG4YC6arn2 |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
ARedirect Chain1 redirect(s), 417 ms totalPASS
https://fourseasons.com
317 ms · HTTP/1.1
https://www.fourseasons.com:443/
101 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://fourseasons.com | 301 | 317 ms | HTTP/1.1 | awselb/2.0 |
| 2 | https://www.fourseasons.com:443/ | 403 | 101 ms | HTTP/1.1 | AkamaiGHost |
See the visual redirect chain in the HTTP Probe tab →
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencefourseasons.com — via CSC Corporate Domains, Inc., 29 years, 7 months old, hosted on AWSPASS
201 days
February 4, 2027
131 days
Issued by Sectigo Limited
29 years, 7 months
Registered February 3, 1997
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
16.54.79.180
CSC Corporate Domains, Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.
Learn more ▾ ▴
DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.
Source: ICANN / RFC 4033
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.
Learn more ▾ ▴
Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.
Source: ICANN / domain-security best practice