Skip to content
https://blog.hypercrites.de

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
10
PASS
6
INFO
0
Probed from Sao Paulo, Brazil
200 OK
Checks
17
6 PASS 10 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
DNS Records
1 A records, 440 ms lookup
REVIEW
1 A records, 440 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 91.67.48.143
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
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: hypercrites.de
Info::
2 nameserver(s) configured
Got: docks02.rzone.de, shades07.rzone.de
Info::
1 mail exchanger(s) configured
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Warning::
DNS resolution is slow (440 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 440 ms
A91.67.48.143
AAAA—
CNAMEhypercrites.de
NSdocks02.rzone.de, shades07.rzone.de
MX
5 smtpin.rzone.de
TXT
google-site-verification=AwRdIX70JYLsg4l-bRWQ2VGkS1OZO0mPlyN6rgvxa6Y
CAALookup not available with standard resolver
Resolved in 440 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

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

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)

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

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 91.67.48.143 does not match any cert SAN: ip5b43308f.dynamic.kabel-deutschland.de
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
C
Multi-Resolver DNS Speed
Action
Mean 299ms across 3 resolvers (spread 267ms)
REVIEW
Mean 299ms across 3 resolvers (spread 267ms)
Info::
Google: 137ms
Got: 137ms via 8.8.8.8:53
Info::
Cloudflare: 357ms
Got: 357ms via 1.1.1.1:53
Info::
Quad9: 404ms
Got: 404ms via 9.9.9.9:53
Info::
High latency spread between resolvers: 267ms (min 137ms / max 404ms)
Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.
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

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

Connection waterfall

DNS Lookup 449 ms TCP Connect 219 ms TLS Handshake 225 ms Server Processing 240 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
67 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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 Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://blog.hypercrites.de

https://blog.hypercrites.de

1484 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://blog.hypercrites.de2001484 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 7 URLs
PASS
robots.txt present, sitemap with 7 URLs
Info::
robots.txt is present
Got: 1937 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 7 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1937 B Sitemaps referenced 1 User-agents Google-CloudVertexBot, QuillBot, ImagesiftBot, YouBot, Applebot, Operator, panscient.com, SBIntuitionsBot, Scrapy, TikTokSpider, Claude-Web, FacebookBot, ISSCyberRiskCrawler, Perplexity-User, VelenPublicWebCrawler, bedrockbot, Brightbot 1.0, ChatGPT-User, FriendlyCrawler, GoogleOther-Video, meta-externalagent, Sidetrade indexer bot, aiHitBot, Kangaroo Bot, omgilibot, QualifiedBot, ClaudeBot, Factset_spyderbot, iaskspider/2.0, Panscient, SemrushBot-SWA, Andibot, omgili, YandexAdditionalBot, img2dataset, Meta-ExternalAgent, MistralAI-User/1.0, OAI-SearchBot, PhindBot, Timpibot, quillbot.com, CCBot, Meta-ExternalFetcher, NovaAct, YandexAdditional, FirecrawlAgent, AI2Bot, Applebot-Extended, cohere-training-data-crawler, Diffbot, GoogleOther-Image, GPTBot, Claude-SearchBot, meta-externalfetcher, PetalBot, SemrushBot-OCOB, Bytespider, Cotoyogi, Google-Extended, ICC-Crawler, PanguBot, *, cohere-ai, Webzio-Extended, Ai2Bot-Dolma, GoogleOther, PerplexityBot, wpbot, Amazonbot, anthropic-ai, Claude-User, Crawlspace, DuckAssistBot Blocking No — crawling allowed
User-agent: AI2Bot
User-agent: Ai2Bot-Dolma
User-agent: aiHitBot
User-agent: Amazonbot
User-agent: Andibot
User-agent: anthropic-ai
User-agent: Applebot
User-agent: Applebot-Extended
User-agent: bedrockbot
User-agent: Brightbot 1.0
User-agent: Bytespider
User-agent: CCBot
User-agent: ChatGPT-User
User-agent: Claude-SearchBot
User-agent: Claude-User
User-agent: Claude-Web
User-agent: ClaudeBot
User-agent: cohere-ai
User-agent: cohere-training-data-crawler
User-agent: Cotoyogi
User-agent: Crawlspace
User-agent: Diffbot
User-agent: DuckAssistBot
User-agent: FacebookBot
User-agent: Factset_spyderbot
User-agent: FirecrawlAgent
User-agent: FriendlyCrawler
User-agent: Google-CloudVertexBot
User-agent: Google-Extended
User-agent: GoogleOther
User-agent: GoogleOther-Image
User-agent: GoogleOther-Video
User-agent: GPTBot
User-agent: iaskspider/2.0
User-agent: ICC-Crawler
User-agent: ImagesiftBot
User-agent: img2dataset
User-agent: ISSCyberRiskCrawler
User-agent: Kangaroo Bot
User-agent: meta-externalagent
User-agent: Meta-ExternalAgent
User-agent: meta-externalfetcher
User-agent: Meta-ExternalFetcher
User-agent: MistralAI-User/1.0
User-agent: NovaAct
User-agent: OAI-SearchBot
User-agent: omgili
User-agent: omgilibot
User-agent: Operator
User-agent: PanguBot
User-agent: Panscient
User-agent: panscient.com
User-agent: Perplexity-User
User-agent: PerplexityBot
User-agent: PetalBot
User-agent: PhindBot
User-agent: QualifiedBot
User-agent: QuillBot
User-agent: quillbot.com
User-agent: SBIntuitionsBot
User-agent: Scrapy
User-agent: SemrushBot-OCOB
User-agent: SemrushBot-SWA
User-agent: Sidetrade indexer bot
User-agent: TikTokSpider
User-agent: Timpibot
User-agent: VelenPublicWebCrawler
User-agent: Webzio-Extended
User-agent: wpbot
User-agent: YandexAdditional
User-agent: YandexAdditionalBot
User-agent: YouBot
Disallow: /

User-agent: *
Disallow: /img/
Disallow: /postimg/

Sitemap: https://blog.hypercrites.de/sitemap.php
sitemap.xml 200 OK
Type URL Set URLs 7 entries Valid XML Yes
Sample URLs:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.blog.hypercrites.de/
200https://blog.hypercrites.de/

HTTP → HTTPS

301http://blog.hypercrites.de/ → https://blog.hypercrites.de/

Consistent

A+
Domain Intelligence
hypercrites.de — hosted on VODANET International IP-Backbone of Vodafone, DE
PASS
hypercrites.de — hosted on VODANET International IP-Backbone of Vodafone, DE
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: VODANET International IP-Backbone of Vodafone, DE
Got: AS3209
Domain expiry

Unknown

SSL certificate

67 days

Issued by Let's Encrypt

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

VODANET International IP-Backbone of Vodafone, DE

ASN AS3209

91.67.48.143

Registrar

Registrar unknown

Unlocked Name servers unknown
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar
Hosting
IP Address 91.67.48.143
ASN AS3209 (VODANET International IP-Backbone of Vodafone, DE)
Provider VODANET International IP-Backbone of Vodafone, DE
Data source: whois (1.7s)

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+
Health Check Endpoint
Health endpoint at https://blog.hypercrites.de/health (HTTP 200)
PASS
Health endpoint at https://blog.hypercrites.de/health (HTTP 200)
Info::
Public health endpoint at https://blog.hypercrites.de/health
Got: https://blog.hypercrites.de/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback