Skip to content
https://cloudflare.net

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
95
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
7 PASS 2 REVIEW
B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 207 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 207 B Sitemaps referenced 0 User-agents MS Search 6.0 Robot, gsa-crawler, *, Eluta.ca Blocking No — crawling allowed
User-agent: *

Crawl-delay: 10
Allow: /


User-agent: Eluta.ca

Crawl-delay: 60
Allow: /


User-agent: MS Search 6.0 Robot

Crawl-delay: 60
Allow: /


User-agent: gsa-crawler

Crawl-delay: 60
Allow: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
2 A records, 30 ms lookup
PASS
2 A records, 30 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.17.156.85, 104.16.208.90
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6811:9c55, 2606:4700::6810:d05a
Info::
5 nameserver(s) configured
Got: ns4.cloudflare.net, ns2.cloudflare.net, ns5.cloudflare.net, ns3.cloudflare.net, ns1.cloudflare.net
Info::
4 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: 30 ms
Got: 30 ms
A104.17.156.85, 104.16.208.90
AAAA2606:4700::6811:9c55, 2606:4700::6810:d05a
CNAME
NSns4.cloudflare.net, ns2.cloudflare.net, ns5.cloudflare.net, ns3.cloudflare.net, ns1.cloudflare.net
MX
5 mailstream-canary.mxrecord.io
10 mailstream-east.mxrecord.io
10 mailstream-west.mxrecord.io
20 mailstream-central.mxrecord.mx
TXT
google-site-verification=R8oHKw1eGX8BBg8V0jIvsMLOcuPSn2V-DgW-Rnm4pR4
SPF v=spf1 include:_spf.google.com -all
CAALookup not available with standard resolver
Resolved in 30 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), 312 ms total
PASS
1 redirect(s), 312 ms total
Info::
Single redirect
Got: https://cloudflare.net → https://cloudflare.net/home/default.aspx (301)

https://cloudflare.net

107 ms · HTTP/1.1

301

https://cloudflare.net/home/default.aspx

205 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://cloudflare.net301107 msHTTP/1.1cloudflare
2https://cloudflare.net/home/default.aspx200205 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700::6811:9c55, 2606:4700::6810:d05a
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700::6811:9c55, 2606:4700::6810:d05a Connection Reachable (17 ms)
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: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.cloudflare.net/
200https://cloudflare.net/

Preferred variant: non-www

HTTP → HTTPS

301http://cloudflare.net/ https://cloudflare.net/

Consistent

A+
Domain Intelligence
cloudflare.net — via Cloudflare, Inc., 17 years, 4 months old
PASS
cloudflare.net — via Cloudflare, Inc., 17 years, 4 months old
Info::
Domain registered until Feb 17, 2033 (6 years, 11 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Cloudflare, 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.
Domain expiry

2412 days

February 17, 2033

SSL certificate

74 days

Issued by Let's Encrypt

Domain age

17 years, 4 months

Registered February 17, 2009

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700::6810:d05a

Registrar

Cloudflare, Inc.

Unlocked 5 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Cloudflare, Inc.
Created February 17, 2009 (17 years, 4 months ago)
Expires February 17, 2033 (6 years, 11 months)
Last Updated January 11, 2024
Name Servers ns1.cloudflare.net, ns2.cloudflare.net, ns3.cloudflare.net, ns4.cloudflare.net, ns5.cloudflare.net
DNSSEC Enabled
Hosting
IP Address 2606:4700::6810:d05a
Data source: rdap (0.1s)

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 229 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.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
24 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
230 ms
Total Time Total request time from DNS lookup through full response.
230 ms

Connection waterfall

DNS Lookup 30 ms TCP Connect 17 ms TLS Handshake 24 ms Server Processing 158 ms Content Transfer 0 ms
A+
CDN & Delivery
Cloudflare (HIT)
PASS
Cloudflare (HIT)
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9ed4bd8a085ebb39-CDG
Info::
CDN cache status: HIT
CDN Detected: Cloudflare
Provider Cloudflare Cache Status HIT Evidence cf-ray: 9ed4bd8a085ebb39-CDG
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback