Skip to content
https://aboutamazon.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.aboutamazon.com/
200https://aboutamazon.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://aboutamazon.com/ → https://aboutamazon.com:443/

Consistent

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

Certificate validity

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

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 Records
3 A records, 39 ms lookup
PASS
3 A records, 39 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 52.86.181.79, 100.51.250.27, 3.225.117.62
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-829.awsdns-39.net, ns-221.awsdns-27.com, ns-1630.awsdns-11.co.uk, ns-1135.awsdns-13.org
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::
SPF record present in TXT
Info::
DNS resolution time: 39 ms
Got: 39 ms
A52.86.181.79, 100.51.250.27, 3.225.117.62
AAAA—
CNAME—
NSns-829.awsdns-39.net, ns-221.awsdns-27.com, ns-1630.awsdns-11.co.uk, ns-1135.awsdns-13.org
MX—
TXT
pardot897621=8cbfe93d2a1404ef2fbffca09f965e37aba92366489db2e98f429c997117f1dc
SPF v=spf1 -all
sending_domain105672=80653c8d9689b6a530c0fa945714082ac2160c531a140cd67264560d302...
google-site-verification=cnSXpz0TIFyk-QyIYfjVPYHwx7T-k51GelN7b6Gkcms
adobe-idp-site-verification=46496b741180b6d655437bf03ca0495f5c42ff4ad7f901894519...
pardot924742=4a2abfd87556140d93b4c31eba97bb0480b0ae9ba78eed9ce0f70d649342c6e7
sending_domain637851=540f4b25dae384796966c0a6402ba10db50bd3a9a7a17ada080f556f156...
pardot637851=ba00f08906642887053ba51b76d709ba2a37a17fb4ef943ac14a79261bf1de5b
CAALookup not available with standard resolver
Resolved in 39 ms

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.

A
Redirect Chain
1 redirect(s), 426 ms total
PASS
1 redirect(s), 426 ms total
Info::
Single redirect
Got: https://aboutamazon.com → https://www.aboutamazon.com:443/ (301)
Info::
WWW normalization redirect

https://aboutamazon.com

292 ms · HTTP/1.1

301

https://www.aboutamazon.com:443/

135 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://aboutamazon.com301292 msHTTP/1.1awselb/2.0
2https://www.aboutamazon.com:443/200135 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 127 URLs
PASS
robots.txt present, sitemap with 127 URLs
Info::
robots.txt is present
Got: 132 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 127 entries
Info::
Sitemap index with 127 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 132 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
User-agent: *
Crawl-delay: 10
Sitemap: https://www.aboutamazon.com/sitemap.xml
Sitemap: https://www.aboutamazon.com/news-sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 127 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
aboutamazon.com — via MarkMonitor Inc., 21 years, 5 months old, hosted on AWS
PASS
aboutamazon.com — via MarkMonitor Inc., 21 years, 5 months old, hosted on AWS
Info::
Domain registered until Jan 16, 2027 (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.
Warning::
Registrar lock is NOT enabled
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.
Info::
Hosting: AWS
Got: AS14618
Domain expiry

152 days

January 16, 2027

SSL certificate

140 days

Issued by Amazon

Domain age

21 years, 5 months

Registered February 19, 2005

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

100.51.250.27

Registrar

MarkMonitor Inc.

Unlocked 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created February 19, 2005 (21 years, 5 months ago)
Expires January 16, 2027 (8 months)
Last Updated October 31, 2025
Name Servers ns-1135.awsdns-13.org, ns-1630.awsdns-11.co.uk, ns-221.awsdns-27.com, ns-829.awsdns-39.net
DNSSEC Not enabled
Hosting
IP Address 100.51.250.27
ASN AS14618 (AMAZON-AES - 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

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.

Why this matters

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

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.
46 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
98 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
99 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
341 ms
Total Time Total request time from DNS lookup through full response.
341 ms

Connection waterfall

DNS Lookup 46 ms TCP Connect 98 ms TLS Handshake 99 ms Server Processing 98 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback