Skip to content
https://haxx.se

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Sao Paulo, Brazil
200 OK
Checks
9
4 PASS 4 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.

B
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

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

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

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.haxx.se/
200https://haxx.se/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://haxx.se/ → https://haxx.se/

Consistent

B
HTTP Probe Timing
Total 1170 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
470 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
231 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
237 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.17 s
Total Time Total request time from DNS lookup through full response.
1.17 s

Connection waterfall

DNS Lookup 470 ms TCP Connect 231 ms TLS Handshake 237 ms Server Processing 232 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
73 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
1 A records, 468 ms lookup
PASS
1 A records, 468 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 159.253.31.95
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a02:750:7:3305::2aa
Info::
2 nameserver(s) configured
Got: ns1.haxx.se, ns.amplitut.de
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
Warning::
DNS resolution is slow (468 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 468 ms
A159.253.31.95
AAAA2a02:750:7:3305::2aa
CNAME—
NSns1.haxx.se, ns.amplitut.de
MX
10 silly.haxx.se
TXT
SPF v=spf1 a include:_spf.google.com ip4:81.236.60.0/24 ip4:192.44.240.0/21 -all
google-site-verification=maTgcOggUV5uW_uQTqa3GR0xpIfvKHoJ4SPwr8I_EaY
CAALookup not available with standard resolver
Resolved in 468 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://haxx.se

https://haxx.se

934 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://haxx.se200934 msHTTP/1.1nginx/1.27.5
A+
IPv6 Readiness
IPv6 reachable (206 ms)
PASS
IPv6 reachable (206 ms)
Info::
IPv6 is configured and reachable at 2a02:750:7:3305::2aa
Got: 206 ms connect
IPv6 Ready
AAAA Records 2a02:750:7:3305::2aa Connection Reachable (206 ms)
A
Domain Intelligence
haxx.se — via Loopia AB, 26 years, 3 months old
PASS
haxx.se — via Loopia AB, 26 years, 3 months old
Warning::
Domain expires in 31 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires May 23, 2026
Info::
Registrar: Loopia AB
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

EXPIRED

May 23, 2026

SSL certificate

73 days

Issued by Let's Encrypt

Domain age

26 years, 3 months

Registered May 23, 2000

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2a02:750:7:3305::2aa

Registrar

Loopia AB

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Loopia AB
Created May 23, 2000 (26 years, 3 months ago)
Expires May 23, 2026 (1 months)
Last Updated May 5, 2025
Name Servers ns.amplitut.de, ns1.haxx.se
Registrant danhax3571-00001
Hosting
IP Address 2a02:750:7:3305::2aa
Data source: whois (0.8s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback