Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction2 redirect(s), 5408 ms totalFIX
https://subway.com
44 ms · HTTP/1.1
https://www.subway.com/
2083 ms · HTTP/1.1
https://www.subway.com/en-us
3281 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://subway.com | 301 | 44 ms | HTTP/1.1 | Microsoft-IIS/10.0 |
| 2 | https://www.subway.com/ | 302 | 2083 ms | HTTP/1.1 | Microsoft-IIS/10.0 |
| 3 | https://www.subway.com/en-us | 200 | 3281 ms | HTTP/1.1 | Microsoft-IIS/10.0 |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
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 & Recommendations167 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 Records1 A records, 11 ms lookupPASS
| A | 20.49.104.50 |
| AAAA | — |
| CNAME | — |
| NS | a6-64.akam.net, a1-109.akam.net, a11-65.akam.net, a8-66.akam.net, a13-65.akam.net, a16-66.akam.net |
| MX | 10 fwh-mail-onmicrosoft-com.mail.protection.outlook.com |
| TXT | EmEjLLL4QADoazTzqtvan1bv6YMyVFwGL2jNXpikJzhI8o//7A6fOpAcg1iqih5QidRx9U0i2lae15h3... Dynatrace-site-verification=da9ae839-07f7-479f-a048-f3c40b64337c__ovr7cl3o83h6v8... apple-domain-verification=b5CpkBhV8vIzZtP8 ecostruxure-it-verification=650a765a-c7dc-49a6-85ef-63d7ae790f21 d365mktkey=27h4szq8axqtjclmkrdhoydvx amazonses:rfeDc6IPwWwqIeXxLTkMIFIehh1+o5FR+AEIBPo+aDM= Dynatrace-site-verification=37764e30-4ee4-403b-a66b-f2dacc3a7734__6vthkjdn478aft... facebook-domain-verification=9411x4korp3etqeg7zd5ihfmhimgbz anthropic-domain-verification-111pyz=1nPjXqAfargZnEgGLARKRSDUr _qqdjbhl6yfl1s6qu8m3rbju0h907lny onetrust-domain-verification=e353972587624065aec066201135b725 _xb3hf9ozq4ftpre79rej7cr3hdm9xnk d365mktkey=4vh8zlupmija2mggwyfzad1yv 3bcvb797i9bokin5jdb6np2r3k amazonses:lQ7e4of+cGMztoZEmpEpxOv439FwHEC4BXhcspQhdY4= jamf-site-verification=8LRBBQ03vXBLvd73kMnJfA CpWwpQX5DV75F+ZKWAyCyNDUxbYo4InxXeA0PTtdjTCuoo1nm1F6BnEU/LMCxoQsHSQEcffbI4tufAWu... smartsheet-site-validation=WtEHNAAL4WG877SNeundsGrK2ks3oevQ v7cehmoklrdicplaf13ac8k2ua google-site-verification=bUgaQaOMKw_x8QqEELf8-07tgm1Rk0ojsUl0wJr7qJ8 SPF v=spf1 mx ip4:67.20.173.128/26 include:spf.protection.outlook.com ~all postman-domain-verification=5e170be124ac49506592a4877255b533a56f7ed12bd9259f527d... tlJrgGGNYW1T6TOpf3LBRcwsOaS3gelSZgfy60SdzvpTW5WpiAHY4v/hdv/R7WxtcYJ7HF1bBKjSFk7i... amazonses:IVt2mlynAK3WsbvNCsXkHJ/Jwoec4Vn7PuhiYJpSGt8= onetrust-domain-verification=0423cc8be9fc48a6a8221dbb3b6df59d apple-domain-verification=ZePlie9LX2l3lM7J _wfmjcqncwns5kjc701z1274fe51b4p9 cloudhealth=b7d0679d-5571-410b-8073-7c7483a0aed9 apple-domain-verification=oeE28ZHe_eQoKq4vPnj1g-ZEqQBgf55X9GyfpeOh5qs _m9mz38zyi79jntjchyy474p39sqhp2k docusign=5d070834-6746-415f-8a1c-48a729c4928e amazonses:WouvrcaLNwm9MeOA8mPHl3iSO4PJt4GRJpbhFF3crDw= GtuUJJbOSsufY0shVDZxs5FXpBrxJCCVyF/V3rBqKtzqdGEdfAfFd/cx8n7J71VUE1GGoDLjFYW44q5u... MS=ms45332749 _rrkgo7ymt9tvgtbyc18htgca1uymclb flfivcv809cpb8tv46a1ims5pa 2paqitupt4v2gfj371i85act53 adobe-idp-site-verification=c780fdf0a32f6f8ca3d2aed6a01d69016c27b9182374f34214ba... |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
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.
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencesubway.com — via CSC Corporate Domains, Inc., 30 years, 8 months old, hosted on Microsoft AzurePASS
188 days
January 18, 2027
167 days
Issued by DigiCert Inc
30 years, 8 months
Registered January 17, 1996
Not enabled
Protects against DNS spoofing
Microsoft Azure
ASN AS8075
20.49.104.50
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