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

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
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:234c:ba00:6:d0d2:780:93a1, 2600:9000:234c:c00:6:d0d2:780:93a1, 2600:9000:234c:200:6:d0d2:780:93a1, 2600:9000:234c:b200:6:d0d2:780:93a1, 2600:9000:234c:a00:6:d0d2:780:93a1, 2600:9000:234c:f400:6:d0d2:780:93a1, 2600:9000:234c:e800:6:d0d2:780:93a1, 2600:9000:234c:c800:6:d0d2:780:93a1
Info::
IPv6 connection error
Got: dial tcp6 [2600:9000:234c:ba00:6:d0d2:780:93a1]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2600:9000:234c:ba00:6:d0d2:780:93a1, 2600:9000:234c:c00:6:d0d2:780:93a1, 2600:9000:234c:200:6:d0d2:780:93a1, 2600:9000:234c:b200:6:d0d2:780:93a1, 2600:9000:234c:a00:6:d0d2:780:93a1, 2600:9000:234c:f400:6:d0d2:780:93a1, 2600:9000:234c:e800:6:d0d2:780:93a1, 2600:9000:234c:c800:6:d0d2:780: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
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.brave.com/
200https://brave.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A
DNS Records
4 A records, 11 ms lookup
PASS
4 A records, 11 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 108.138.246.94, 108.138.246.58, 108.138.246.65, 108.138.246.105
Info::
Has 8 IPv6 (AAAA) record(s)
Got: 2600:9000:234c:ba00:6:d0d2:780:93a1, 2600:9000:234c:c00:6:d0d2:780:93a1, 2600:9000:234c:200:6:d0d2:780:93a1, 2600:9000:234c:b200:6:d0d2:780:93a1, 2600:9000:234c:a00:6:d0d2:780:93a1, 2600:9000:234c:f400:6:d0d2:780:93a1, 2600:9000:234c:e800:6:d0d2:780:93a1, 2600:9000:234c:c800:6:d0d2:780: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: d16w0ph6f167fi.cloudfront.net
Info::
4 nameserver(s) configured
Got: ns-1445.awsdns-52.org, ns-2029.awsdns-61.co.uk, ns-363.awsdns-45.com, ns-774.awsdns-32.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'.
Info::
DNS resolution time: 11 ms
Got: 11 ms
A108.138.246.94, 108.138.246.58, 108.138.246.65, 108.138.246.105
AAAA2600:9000:234c:ba00:6:d0d2:780:93a1, 2600:9000:234c:c00:6:d0d2:780:93a1, 2600:9000:234c:200:6:d0d2:780:93a1, 2600:9000:234c:b200:6:d0d2:780:93a1, 2600:9000:234c:a00:6:d0d2:780:93a1, 2600:9000:234c:f400:6:d0d2:780:93a1, 2600:9000:234c:e800:6:d0d2:780:93a1, 2600:9000:234c:c800:6:d0d2:780:93a1
CNAMEd16w0ph6f167fi.cloudfront.net
NSns-1445.awsdns-52.org, ns-2029.awsdns-61.co.uk, ns-363.awsdns-45.com, ns-774.awsdns-32.net
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 11 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)

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

https://www.brave.com

25 ms · HTTP/1.1

301

https://brave.com/

16 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.brave.com30125 msHTTP/1.1CloudFront
2https://brave.com/20016 msHTTP/1.1AmazonS3

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 44 URLs
PASS
robots.txt present, sitemap with 44 URLs
Info::
robots.txt is present
Got: 53 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 44 entries
Info::
Sitemap index with 44 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 53 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Sitemap: https://brave.com/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 44 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
brave.com — via NameCheap, Inc., 31 years old, hosted on AWS
PASS
brave.com — via NameCheap, Inc., 31 years old, hosted on AWS
Info::
Domain registered until Sep 17, 2029 (3 years, 5 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: NameCheap, Inc.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

1127 days

September 17, 2029

SSL certificate

190 days

Issued by Amazon

Domain age

31 years

Registered September 18, 1995

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

108.138.246.58

Registrar

NameCheap, Inc.

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar NameCheap, Inc.
Created September 18, 1995 (31 years ago)
Expires September 17, 2029 (3 years, 5 months)
Last Updated November 6, 2023
Name Servers chip.ns.cloudflare.com, kim.ns.cloudflare.com
DNSSEC Enabled
Hosting
IP Address 108.138.246.58
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.1s)
A+
HTTP Probe Timing
Total 27 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
14 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
2 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
6 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
27 ms
Total Time Total request time from DNS lookup through full response.
27 ms

Connection waterfall

DNS Lookup 14 ms TCP Connect 2 ms TLS Handshake 6 ms Server Processing 5 ms Content Transfer 0 ms
A+
CDN & Delivery
AWS CloudFront (Hit from cloudfront)
PASS
AWS CloudFront (Hit from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: SFO5-P1)
Got: x-amz-cf-id: v7a_2Ut9OEmXS2xMV6i_B7cF-PJj7_9qxZPNzZDCCygET3fGmobbpg==
Info::
CDN cache status: Hit from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Hit from cloudfront Evidence x-amz-cf-id: v7a_2Ut9OEmXS2xMV6i_B7cF-PJj7_9qxZPNzZDCCygET3fGmobbpg==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback