Skip to content
https://amazon.com.br

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 3765 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

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

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 3765 B Sitemaps referenced 0 User-agents EtaoSpider, omgili, Brightbot, Claude-SearchBot, CopilotNative, SemrushBot-SWA, Timpibot, DuckAssistBot, Google-Extended, Bytespider, MistralAI-User, Sidetrade indexer bot, aiHitBot, YouBot, Scrapy, Copilot, cohere-ai, FriendlyCrawler, PetalBot, Devin, *, PerplexityBot, GoogleAgent-Mariner, Google-CloudVertexBot, img2dataset, imgproxy, ClaudeBot, Diffbot, meta-externalfetcher, iaskspider, Perplexity-User, Thinkbot, Google-NotebookLM, Ai2Bot-Dolma, GPTBot, CCBot, AI2Bot, PanguBot, wpbot, OAI-SearchBot, meta-externalagent, CopilotSapphire, ChatGPT-User, GoogleAgent-Shopping, Gemini-Deep-Research, VelenPublicWebCrawler, Claude-User, ISSCyberRiskCrawler Blocking No — crawling allowed
User-agent: *
Allow: /*/dp/
Allow: /gp/adlp/
Allow: /gp/aw/kindle/first
Allow: /gp/aw/mom/signup
Allow: /gp/aw/ybh
Allow: /gp/baby-reg
Allow: /gp/cobrandcard/marketing.html
Allow: /gp/coins/earn
Allow: /gp/communication-manager/inbox.html
Allow: /gp/css/gc/payment/redeem-gc-balance
Allow: /gp/css/homepage.html
Allow: /gp/css/order-history
Allow: /gp/digital/ep-landing-page
Allow: /gp/digital/fiona/kcp-landing-page
Allow: /gp/drive/app-download
Allow: /gp/goldbox
Allow: /gp/help
Allow: /gp/history
Allow: /gp/mom/signup
Allow: /gp/prime/pipeline/prime_gifting_landing
Allow: /gp/product/
Allow: /gp/sign-in.html
Allow: /gp/tradein/your-account
Allow: /gp/video/library
Allow: /gp/video/watchlist
Allow: /gp/vine/help
Allow: /help/kindlecloudreader
Allow: /help/kindlefire
Allow: /iss/credit/rewardscardmember
Allow: /iss/credit/storecardmember
Allow: /kindlefirst
Allow: /kindlepersonaldocuments
Allow: /manageyourkindle
Allow: /mn/dcw/myx.html
Allow: /mytv
Allow: /oc/dash-button
Allow: /returns
Allow: /robots.txt
Allow: /s/
Allow: /s?
Allow: /*/s/
Allow: /*/s?
Allow: /sitemaps
Allow: /storecard
Allow: /gp/aw/d/
Allow: /your-account
Allow: /your-orders
Disallow: /gp/help/reports/infringement/jquery/handle-notice-submit.html
Disallow: /gp/help/customer/handler/handle-email-submit.html
Disallow: /gp/ask-widget/askWidget
Disallow: /gp/cart 
Disallow: /gp/flex 
Disallow: /gp/product/e-mail-friend 
Disallow: /gp/product/product-availability 
Disallow: /gp/product/rate-this-item
Disallow: /ss/customer-reviews/lighthouse/
Disallow: /hz/leaderboard/top-reviewers/
Disallow: /hz/leaderboard/hall-of-fame/
Disallow: /review/top-reviewers/
Disallow: /review/top-reviewers
Disallow: /review/hall-of-fame
Disallow: /reviews/top-reviewers/
Disallow: /reviews/top-reviewers
Disallow: /reviews/hall-of-fame
Disallow: /hz/help/contact/*/message/$
Disallow: /-/
Disallow: /gp/aw/shoppingAids/
Disallow: /hz/contact-us/ajax/initiate-trusted-contact/

User-agent: EtaoSpider
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: CCBot
Disallow: /

User-Agent: PerplexityBot
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: GoogleAgent-Mariner
Disallow: /

User-agent: GoogleAgent-Shopping
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: meta-externalagent
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: Scrapy
Disallow: /

User-agent: PetalBot
Disallow: /

User-agent: Devin
Disallow: /

User-agent: omgili
Disallow: /

User-agent: AI2Bot
Disallow: /

User-agent: Gemini-Deep-Research
Disallow: /

User-agent: PanguBot
Disallow: /

User-agent: MistralAI-User
Disallow: /

User-agent: Diffbot
Disallow: /

User-agent: Sidetrade indexer bot
Disallow: /

User-agent: Google-NotebookLM
Disallow: /

User-agent: DuckAssistBot
Disallow: /

User-agent: Copilot
Disallow: /

User-agent: Ai2Bot-Dolma
Disallow: /

User-agent: Google-CloudVertexBot
Disallow: /

User-agent: meta-externalfetcher
Disallow: /

User-agent: iaskspider
Disallow: /

User-agent: wpbot
Disallow: /

User-agent: aiHitBot
Disallow: /

User-agent: cohere-ai
Disallow: /

User-agent: FriendlyCrawler
Disallow: /

User-agent: img2dataset
Disallow: /

User-agent: VelenPublicWebCrawler
Disallow: /

User-agent: YouBot
Disallow: /

User-agent: Brightbot
Disallow: /

User-agent: Claude-User
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Claude-SearchBot
Disallow: /

User-agent: Perplexity-User
Disallow: /

User-agent: ISSCyberRiskCrawler
Disallow: /

User-agent: CopilotNative
Disallow: /

User-agent: CopilotSapphire
Disallow: /

User-agent: imgproxy
Disallow: /

User-agent: SemrushBot-SWA
Disallow: /

User-agent: ChatGPT-User
Disallow: /

User-agent: OAI-SearchBot
Disallow: /

User-agent: Timpibot
Disallow: /

User-agent: Thinkbot
Disallow: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

197
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, 41 ms lookup
PASS
3 A records, 41 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 98.87.170.54, 98.82.142.240, 98.87.171.132
Info::
No IPv6 (AAAA) records
Info::
8 nameserver(s) configured
Got: ns2.amzndns.org, ns1.amzndns.co.uk, ns2.amzndns.net, ns2.amzndns.co.uk, ns1.amzndns.net, ns1.amzndns.com, ns2.amzndns.com, ns1.amzndns.org
Info::
1 mail exchanger(s) configured
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: 41 ms
Got: 41 ms
A98.87.170.54, 98.82.142.240, 98.87.171.132
AAAA
CNAME
NSns2.amzndns.org, ns1.amzndns.co.uk, ns2.amzndns.net, ns2.amzndns.co.uk, ns1.amzndns.net, ns1.amzndns.com, ns2.amzndns.com, ns1.amzndns.org
MX
10 amazon-smtp.amazon.com
TXT
TS1760027
sending_domain608861=f96876009bb57ece45e86c59d52c28f91967393e17e129a7bb3c8a27f2b...
sending_domain1003771=40a3cf13d9285f47af298843028872eb6f913b5142a4fe49eba2a19aa4...
sending_domain608861=18353c947ce8c82c819fc41c50497ce3a0e215d37faef7c4722574780be...
google-site-verification=rZsTppH1Nyf4Si2dQxL-wwoyhHzlPXQqJQ022K6ZDT4
sending_domain229492=e09f06a93ab575b878df03f3c73ffc3982f4071049484f1d094df2fe251...
facebook-domain-verification=vuc919xxsqicebwhb1vwivljnpo8wn
MS=ms75478794
MS=ms26144939
canva-site-verification=qQpCCrwKR-xJP6zCUYDr9Q
MS=ms75478794|
liveramp-site-verification=jZJKgMEQ_1mdjMhKj02iqNACZ-NJHRWhCEQdQ_OuCMo
sending_domain1003771=8db398f9027bd314c1cc4594ed5c69524b7cd13231da05c6342f50f6b4...
SPF v=spf1 include:amazon.com -all
google-site-verification=GetC2weV2ix93Qn6NZB5pfa_USfIa9utVUO6aaBddmY
sending_domain229492=de46cbd47ae39b4d289e2f4d7abdfca420badac47b9260e0fa54fff56d0...
spf2.0/pra include:amazon.com -all
CAALookup not available with standard resolver
Resolved in 41 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), 378 ms total
PASS
1 redirect(s), 378 ms total
Info::
Single redirect
Got: https://amazon.com.br → https://www.amazon.com.br/ (301)
Info::
WWW normalization redirect

https://amazon.com.br

293 ms · HTTP/1.1

301

https://www.amazon.com.br/

85 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://amazon.com.br301293 msHTTP/1.1Server
2https://www.amazon.com.br/20285 msHTTP/1.1CloudFront

See the visual redirect chain in the HTTP Probe tab →

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

202https://www.amazon.com.br/
200https://amazon.com.br/

HTTP → HTTPS

301http://amazon.com.br/ https://amazon.com.br/

Consistent

A+
Domain Intelligence
amazon.com.br — 31 years old, hosted on AWS
PASS
amazon.com.br — 31 years old, hosted on AWS
Info::
Domain registered until Sep 27, 2026 (5 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.
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

75 days

September 27, 2026

SSL certificate

197 days

Issued by Amazon

Domain age

31 years

Registered September 27, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

98.87.171.132

Registrar

Registrar unknown

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar
Created September 27, 1995 (31 years ago)
Expires September 27, 2026 (5 months)
Last Updated September 17, 2025
Name Servers ns2.amzndns.com, ns2.amzndns.net, ns2.amzndns.org, ns2.amzndns.co.uk
DNSSEC Not enabled
Registrant Amazon Servicos de Varejo do Brasil Ltda.
Hosting
IP Address 98.87.171.132
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (1.5s)

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 321 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
30 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
96 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
100 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
322 ms
Total Time Total request time from DNS lookup through full response.
322 ms

Connection waterfall

DNS Lookup 30 ms TCP Connect 96 ms TLS Handshake 100 ms Server Processing 96 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