Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BRedirect Chain2 redirect(s), 84 ms totalREVIEW
https://amtrak.com
20 ms · HTTP/1.1
https://www.amtrak.com/
34 ms · HTTP/1.1
https://www.amtrak.com/home
30 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://amtrak.com | 301 | 20 ms | HTTP/1.1 | AkamaiGHost |
| 2 | https://www.amtrak.com/ | 301 | 34 ms | HTTP/1.1 | AkamaiGHost |
| 3 | https://www.amtrak.com/home | 200 | 30 ms | HTTP/1.1 |
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
BTLS Certificate Expiry & Recommendations168 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- 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
BCDN & DeliveryAkamaiREVIEW
A+DNS Records1 A records, 13 ms lookupPASS
| A | 184.24.23.89 |
| AAAA | 2a02:26f0:1180:184::1860, 2a02:26f0:1180:188::1860 |
| CNAME | — |
| NS | a26-67.akam.net, a10-65.akam.net, a1-62.akam.net, a3-64.akam.net, a2-66.akam.net, a9-65.akam.net |
| MX | 0 mx1.hc2612-17.iphmx.com 0 mx2.hc2612-17.iphmx.com |
| TXT | google-site-verification=RINi4O6tAsn3wxPf1R89M2SQed-Xyoo-Ri7xDYqNnJU MS=301545433FA1E4126BB6C72EFB8D592AFA20B4CA bw=WVk8lecSL1wSvabPx6XsDBRjN6N7PX2RfTnWYlkRwgNT MS=ms76818831 ms-domain-verification=1fceff79-0683-4610-9553-7d9d829943cb MS=ms13076239 _whz1vpn6qv5yhwcy7ez8vxu4i8iumwx _noyplul4olb0n3bb7dv8ltn93s0bbc9 SPF v=spf1 ip4:70.33.172.36 ip4:174.129.192.189 ip4:174.129.8.146 ip4:12.7.225.18 ip... teamviewer-sso-verification=493792d9f4304862bd09db7d4b528bad Dynatrace-site-verification=2b27ef9f-4326-4c67-ac97-db68f75bff42__1h8g3c6tjuii7o... _nwtmjqwjxbh8szvpqryc1ieu4ie04us atlassian-domain-verification=845JZNWKeTEHg62xWmy8YCOkKI1gD/IWg4w4/HGtqjwazzGP7G... google-gws-recovery-domain-verification=49529359 p21DeRGccWrXF4st2xyy1hPLBVpO9+Ya4010c1Kt4P1cHNFqWZD5h5DfohbygQXz2Ma7l9dcHtFqBef6... MS=ms65892260 ms-domain-verification=2d55fd47-2e5b-41b7-a198-7c6ebace5d19 |
| 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+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 1633 URLsPASS
Sitemap: https://www.amtrak.com/sitemap.xml
User-agent: *
Disallow: /account-overview/*
Disallow: /account-overview
Disallow: /home/welcome
Disallow: /servlet/*
Disallow: /reference-data/*
Disallow: /api/*
Disallow: /ibcontent/*
Disallow: /test-target/*
Disallow: /archive/*
Disallow: /tcversion/*
Disallow: /ContentMigration
Disallow: /services/*
Disallow: /wifi/*
Disallow: /future-layouts/*
Disallow: /documents/documents/*
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligenceamtrak.com — via Network Solutions, LLC, 31 years, 7 months oldPASS
1332 days
February 7, 2030
168 days
Issued by DigiCert Inc
31 years, 7 months
Registered February 6, 1995
Not enabled
Protects against DNS spoofing
Unknown
2a02:26f0:6d00:586::1860
Network Solutions, LLC
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