Skip to content
https://www.toyota.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Amsterdam, Netherlands
200 OK
Checks
9
6 PASS 2 REVIEW 1 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2600:9000:2447:1800:9:3aa4:d340:93a1, 2600:9000:2447:ca00:9:3aa4:d340:93a1, 2600:9000:2447:5400:9:3aa4:d340:93a1, 2600:9000:2447:2c00:9:3aa4:d340:93a1, 2600:9000:2447:4a00:9:3aa4:d340:93a1, 2600:9000:2447:cc00:9:3aa4:d340:93a1, 2600:9000:2447:f800:9:3aa4:d340:93a1, 2600:9000:2447:3a00:9:3aa4:d340:93a1
Info::
IPv6 connection error
Got: dial tcp6 [2600:9000:2447:1800:9:3aa4:d340:93a1]:443: connect: no route to host
IPv6 Misconfigured
AAAA Records 2600:9000:2447:1800:9:3aa4:d340:93a1, 2600:9000:2447:ca00:9:3aa4:d340:93a1, 2600:9000:2447:5400:9:3aa4:d340:93a1, 2600:9000:2447:2c00:9:3aa4:d340:93a1, 2600:9000:2447:4a00:9:3aa4:d340:93a1, 2600:9000:2447:cc00:9:3aa4:d340:93a1, 2600:9000:2447:f800:9:3aa4:d340:93a1, 2600:9000:2447:3a00:9:3aa4:d340:93a1 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

B
DNS Records
4 A records, 288 ms lookup
REVIEW
4 A records, 288 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 54.230.114.90, 54.230.114.129, 54.230.114.72, 54.230.114.88
Info::
Has 8 IPv6 (AAAA) record(s)
Got: 2600:9000:2447:1800:9:3aa4:d340:93a1, 2600:9000:2447:ca00:9:3aa4:d340:93a1, 2600:9000:2447:5400:9:3aa4:d340:93a1, 2600:9000:2447:2c00:9:3aa4:d340:93a1, 2600:9000:2447:4a00:9:3aa4:d340:93a1, 2600:9000:2447:cc00:9:3aa4:d340:93a1, 2600:9000:2447:f800:9:3aa4:d340:93a1, 2600:9000:2447:3a00:9:3aa4:d340:93a1
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: dzo9ysms19bgt.cloudfront.net
Info::
4 nameserver(s) configured
Got: ns-1038.awsdns-01.org, ns-1930.awsdns-49.co.uk, ns-243.awsdns-30.com, ns-726.awsdns-26.net
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Warning::
DNS resolution is slow (288 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 288 ms
A54.230.114.90, 54.230.114.129, 54.230.114.72, 54.230.114.88
AAAA2600:9000:2447:1800:9:3aa4:d340:93a1, 2600:9000:2447:ca00:9:3aa4:d340:93a1, 2600:9000:2447:5400:9:3aa4:d340:93a1, 2600:9000:2447:2c00:9:3aa4:d340:93a1, 2600:9000:2447:4a00:9:3aa4:d340:93a1, 2600:9000:2447:cc00:9:3aa4:d340:93a1, 2600:9000:2447:f800:9:3aa4:d340:93a1, 2600:9000:2447:3a00:9:3aa4:d340:93a1
CNAMEdzo9ysms19bgt.cloudfront.net
NSns-1038.awsdns-01.org, ns-1930.awsdns-49.co.uk, ns-243.awsdns-30.com, ns-726.awsdns-26.net
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 288 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

B
TLS Certificate Expiry & Recommendations
241 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

241
days left
0d 30d 60d 90d+

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • 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
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.toyota.com

https://www.toyota.com

30 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.toyota.com20030 msHTTP/1.1Apache
A+
Crawlability
robots.txt present, sitemap with 20 URLs
PASS
robots.txt present, sitemap with 20 URLs
Info::
robots.txt is present
Got: 1375 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 20 entries
Info::
Sitemap index with 20 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1375 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# 2025-03-20

User-agent: *
Disallow: /akamai/
Disallow: /campaigns/
Disallow: /apps/recruiting/
Disallow: /analytics/
Disallow: /search/
Disallow: /toyotaSearch/
Disallow: /byt4/pub/
Disallow: /byt/
Disallow: /dealer-inventory/
Disallow: /espanol/dealer-inventory/
Disallow: /hris/HRPolicy.htm
Disallow: /owners/web/pages/home?p_auth=* 
Disallow: /owners/web/pages/parts-service/service-offers?p_auth=* 
Disallow: /owners/web/pages/parts-service/service-offers?p_p_auth=* 
Disallow: /owners/parts-service/toyota-service-care
Disallow: /t3portal/
Disallow: /t3Portal/
Disallow: /responsive/
Disallow: /stylish-cars/
Disallow: /capable-suvs/
Disallow: /rugged-trucks/
Disallow: /powerful-hybrid-suvs/
Disallow: /espanol/stylish-cars/
Disallow: /espanol/capable-suvs/
Disallow: /espanol/rugged-trucks/
Disallow: /espanol/powerful-hybrid-suvs/
Disallow: /_tcm/
Disallow: /content/ebrochure/toyota-mobility.pdf
Disallow: /content/dam/toyota/brochures/pdf/tcom/toyota-mobility.pdf
Disallow: /firmware-updates/download
Disallow: /firmware-updates/updates
Disallow: /firmware-updates/usb-steps
Disallow: /iframe-test
Disallow: /resources/smartpath/
Disallow: /espanol/resources/smartpath/
Disallow: /resources/rct/
Disallow: /espanol/resources/rct/
Disallow: /vehicles/
Disallow: /espanol/vehicles/
Disallow: /configurator/*zipcode=

Sitemap: http://www.toyota.com/sitemap_index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 20 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.toyota.com/
301https://toyota.com/

Preferred variant: www

HTTP → HTTPS

301http://www.toyota.com/ → https://www.toyota.com/

Consistent

A+
Domain Intelligence
toyota.com — via MarkMonitor Inc., 31 years, 8 months old, hosted on AWS
PASS
toyota.com — via MarkMonitor Inc., 31 years, 8 months old, hosted on AWS
Info::
Domain registered until Dec 28, 2027 (1 years, 8 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: MarkMonitor Inc.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

580 days

December 28, 2027

SSL certificate

241 days

Issued by Amazon

Domain age

31 years, 8 months

Registered December 29, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

76.223.71.125

Registrar

MarkMonitor Inc.

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar MarkMonitor Inc.
Created December 29, 1994 (31 years, 8 months ago)
Expires December 28, 2027 (1 years, 8 months)
Last Updated December 9, 2025
Name Servers pdns102.ultradns.biz, pdns102.ultradns.com, pdns102.ultradns.net, pdns102.ultradns.org
DNSSEC Not enabled
Hosting
IP Address 76.223.71.125
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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

A+
HTTP Probe Timing
Total 341 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
283 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
10 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
15 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
329 ms
Total Time Total request time from DNS lookup through full response.
341 ms

Connection waterfall

DNS Lookup 283 ms TCP Connect 10 ms TLS Handshake 15 ms Server Processing 22 ms Content Transfer 13 ms
A+
CDN & Delivery
AWS CloudFront (Hit from cloudfront)
PASS
AWS CloudFront (Hit from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: CDG54-P2)
Got: x-amz-cf-id: JcvDtaauLmjQMPHJvo3KU7ilYXwvIqqEzIhJsIKcXMigQr3i-s4i-Q==
Info::
CDN cache status: Hit from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Hit from cloudfront Evidence x-amz-cf-id: JcvDtaauLmjQMPHJvo3KU7ilYXwvIqqEzIhJsIKcXMigQr3i-s4i-Q==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback