Skip to content
https://bloggersdelight.dk

Infrastructure

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

C
Crawlability
Action
robots.txt present, sitemap with 7 URLs
REVIEW
robots.txt present, sitemap with 7 URLs
Info::
robots.txt is present
Got: 154 bytes
Critical::
robots.txt blocks all crawlers
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 7 entries
Info::
Sitemap index with 7 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.

Learn more

Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.

Source: 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 154 B Sitemaps referenced 0 User-agents Googlebot, * Blocking Yes — all crawlers blocked
# Allows all google bots including ones that does not match "Googlebot"
User-agent: Googlebot
Disallow:

# Block all other bots
User-agent: *
Disallow: /

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

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
B
CDN & Delivery
Varnish
REVIEW
Varnish
Info::
Site is served via Varnish CDN
Got: via: 1.1 8f0766119d6b (Varnish/7.7)
CDN Detected: Varnish
Provider Varnish Evidence via: 1.1 8f0766119d6b (Varnish/7.7)
A+
DNS Records
1 A records, 61 ms lookup
PASS
1 A records, 61 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 49.12.130.166
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns01.one.com, ns02.one.com
Info::
7 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: 61 ms
Got: 61 ms
A49.12.130.166
AAAA
CNAME
NSns01.one.com, ns02.one.com
MX
10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
20 alt2.aspmx.l.google.com
30 aspmx2.googlemail.com
30 aspmx5.googlemail.com
30 aspmx4.googlemail.com
30 aspmx3.googlemail.com
TXT
_eogdzbn99npfb9ak916u1whzs62wbcp
_qiovhwp2ij7qvegsjfrf8vf256qodvw
google-site-verification=VXcmfBZ5uscdsjMkO4O4nce6CRMS1ktrKyHb_xb31Zo
SPF v=spf1 ip4:88.198.0.123 ip4:88.198.47.207 ip4:49.12.130.166 ip4:49.12.130.165 ip...
google-site-verification=-su6VtSj0DrTLNk4hxqWJJTuu3xY5cWgJT8zS_ZHHTE
google-site-verification=CKR3rzmvar3ddE3UX7tI6tzPPf9_VxAnRMFLYppf0j0
CAALookup not available with standard resolver
Resolved in 61 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.

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

https://bloggersdelight.dk

132 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://bloggersdelight.dk200132 msHTTP/1.1Apache/2.4.29 (Ubuntu)
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.bloggersdelight.dk/
200https://bloggersdelight.dk/

Preferred variant: non-www

HTTP → HTTPS

301http://bloggersdelight.dk/ https://bloggersdelight.dk/

Consistent

A+
Domain Intelligence
bloggersdelight.dk — 15 years, 9 months old, hosted on Hetzner
PASS
bloggersdelight.dk — 15 years, 9 months old, hosted on Hetzner
Info::
Domain registered until Sep 30, 2028 (2 years, 5 months remaining)
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: Hetzner
Got: AS24940
Domain expiry

809 days

September 30, 2028

SSL certificate

76 days

Issued by DigiCert Inc

Domain age

15 years, 9 months

Registered September 28, 2010

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Hetzner

ASN AS24940

49.12.130.166

Registrar

Registrar unknown

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
Created September 28, 2010 (15 years, 9 months ago)
Expires September 30, 2028 (2 years, 5 months)
Name Servers ns01.one.com, ns02.one.com
Hosting
IP Address 49.12.130.166
ASN AS24940 (HETZNER-AS, DE)
Provider Hetzner
Data source: whois (0.6s)

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

Connection waterfall

DNS Lookup 61 ms TCP Connect 29 ms TLS Handshake 67 ms Server Processing 31 ms Content Transfer 1 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback