Skip to content
https://handle.net

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Amsterdam, Netherlands
200 OK
Checks
9
6 PASS 3 REVIEW
B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 56 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 56 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /not_used/
Disallow: /resolver/

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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.handle.net/
200https://handle.net/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://handle.net/ https://handle.net/

Consistent

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

Certificate validity

82
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
2 A records, 7 ms lookup
PASS
2 A records, 7 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 188.114.96.0, 188.114.97.0
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a06:98c1:3120::, 2a06:98c1:3121::
Info::
2 nameserver(s) configured
Got: brad.ns.cloudflare.com, linda.ns.cloudflare.com
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: 7 ms
Got: 7 ms
A188.114.96.0, 188.114.97.0
AAAA2a06:98c1:3120::, 2a06:98c1:3121::
CNAME
NSbrad.ns.cloudflare.com, linda.ns.cloudflare.com
MX
5 mail.cnri.net
TXT
OSSRH-52068
SPF v=spf1 mx ip4:23.25.109.33/28 ip4:64.4.102.182/30 ip4:209.145.85.65/26 ip4:67.22...
CAALookup not available with standard resolver
Resolved in 7 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://handle.net

https://handle.net

325 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://handle.net200325 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2a06:98c1:3120::, 2a06:98c1:3121::
Got: 1 ms connect
IPv6 Ready
AAAA Records 2a06:98c1:3120::, 2a06:98c1:3121:: Connection Reachable (1 ms)
A+
Domain Intelligence
handle.net — via Cloudflare, Inc., 30 years, 5 months old
PASS
handle.net — via Cloudflare, Inc., 30 years, 5 months old
Info::
Domain registered until Apr 13, 2035 (9 years, 1 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

3193 days

April 13, 2035

SSL certificate

82 days

Issued by Google Trust Services

Domain age

30 years, 5 months

Registered April 12, 1996

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2a06:98c1:3120::

Registrar

Cloudflare, Inc.

Unlocked 2 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 April 12, 1996 (30 years, 5 months ago)
Expires April 13, 2035 (9 years, 1 months)
Last Updated September 30, 2025
Name Servers brad.ns.cloudflare.com, linda.ns.cloudflare.com
DNSSEC Enabled
Hosting
IP Address 2a06:98c1:3120::
Data source: rdap (0.0s)

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

Connection waterfall

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

Send Feedback