Skip to content
https://www.golem.de

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
2
REVIEW
6
PASS
9
INFO
0
Probed from Madrid, Spain
302 Found
Checks
17
9 PASS 6 REVIEW 2 FIX
D
Multi-Resolver DNS Speed
Action
Mean 559ms across 3 resolvers (spread 1627ms)
FIX
Mean 559ms across 3 resolvers (spread 1627ms)
Info::
Google: 16ms
Got: 16ms via 8.8.8.8:53
Info::
Quad9: 19ms
Got: 19ms via 9.9.9.9:53
Info::
Cloudflare: 1643ms
Got: 1643ms via 1.1.1.1:53
Info::
High latency spread between resolvers: 1627ms (min 16ms / max 1643ms)
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.
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
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
TLS Certificate Expiry & Recommendations
109 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

109
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.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 503, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A
DNS Records
1 A records, 36 ms lookup
PASS
1 A records, 36 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 77.247.84.129
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: 2a00:13c8:f5::f:4b3d:148
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 36 ms
Got: 36 ms
A77.247.84.129
AAAA2a00:13c8:f5::f:4b3d:148
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 36 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

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)

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A
Reverse DNS
1/2 IPs match cert SAN
PASS
1/2 IPs match cert SAN
Info::
PTR lookup failed for 77.247.84.129: lookup 77.247.84.129: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR for 2a00:13c8:f5::f:4b3d:148 matches certificate SAN: golem.de
A
Redirect Chain
1 redirect(s), 238 ms total
PASS
1 redirect(s), 238 ms total
Info::
Single redirect
Got: https://www.golem.de → https://www.golem.de/sonstiges/zustimmung/auswahl.html?from=https%3A%2F%2Fwww.golem.de%2F (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.golem.de

https://www.golem.de

103 ms · HTTP/1.1

302

https://www.golem.de/sonstiges/zustimmun...

135 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.golem.de302103 msHTTP/1.1nginx
2https://www.golem.de/sonstiges/zustimmun...200135 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A+
IPv6 Readiness
IPv6 reachable (32 ms)
PASS
IPv6 reachable (32 ms)
Info::
IPv6 is configured and reachable at 2a00:13c8:f5::f:4b3d:148
Got: 32 ms connect
IPv6 Ready
AAAA Records 2a00:13c8:f5::f:4b3d:148 Connection Reachable (32 ms)
A+
Crawlability
robots.txt present, sitemap with 343 URLs
PASS
robots.txt present, sitemap with 343 URLs
Info::
robots.txt is present
Got: 3647 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 343 entries
Info::
Sitemap index with 343 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 3647 B Sitemaps referenced 1 User-agents CrawlerBot #SEO, Dotbot #AI, SemrushBot-EO #SEO, Qwantbot-news, YandexMobileBot, Mojeek, Fleebs, ClaudeBot, IABot, DataForSEO #SEO, Netvibes #listening, iask.ai, Ai2Bot #AI, BLEXBot #SEO, MeltwaterNews #listening, SemrushBot-FT #SEO, Yeti, arquivo-web-crawler, AwarioBot #AI, Google-CloudVertexBot, SemrushBot-OCOB #SEO, TaranisAI #monitoring, Uptime-Kuma #monitoring, PressEngineBot #listening, SemrushBot-ESI #SEO, DuckDuckBot, Seekport, GoogleAgent-Mariner, *, AppleNewsBot, Bingbot, Blackbox Exporter #monitoring, Audisto-essential #SEO, Barkrowler #SEO, NoahBot #listening, SemrushBot-BA #SEO, YandexMetrika, OAI-SearchBot, Bytespider, archive.org_bot, InternetArchive, Optimizer #SEO, Applebot, SeznamBot, Heritrix, KrawlerBot #SEO, Neticle Crawler #listening, RyteBot #SEO, SentiBot #listening, SplitSignalBot #SEO, slurp, YandexBot, YandexImages, Dalvik, GoogleOther, PRTG Network Monitor #monitoring, Qwarrybot, SiteAuditBot #SEO, DuckDuckGo, Bravebot, Applebot-Extended, LinkChecker #SEO, PlagAwareBot #plagiate, SemrushBot-SI #SEO, Claude-SearchBot, yacybot, coccocbot, YouBot, img2dataset, MJ12bot #SEO, Pinterestbot #Social, meta-webindexer, Googlebot-Image, PetalBot, GPTBot, BacklinkSpider #SEO, BlogBeatbot #SEO, trendictionbot #listening, Googlebot-News, Googlebot-Video, Diffbot, GoogleOther-Video, SemrushBot #SEO, Googlebot, Amazonbot, PerplexityBot, TimpiBot, VelenPublicWebCrawler, SemrushBot-SWA #SEO, SeobilityBot #SEO, AhrefsBot #SEO, Qwantbot, Baiduspider, Googlebot-Extended, meta-externalagent Blocking No — crawling allowed
# Default
User-Agent: *
Disallow: /mail.php
Disallow: /search.php
Disallow: /search/*
Disallow: /trackback/
Disallow: /news/*.amp.html

# Search Engines / RAG
User-Agent: slurp
User-Agent: DuckDuckBot
User-Agent: DuckDuckGo
User-Agent: Qwantbot
User-Agent: Qwantbot-news
User-Agent: YandexMobileBot
User-Agent: YandexBot
User-Agent: YandexImages
User-Agent: meta-webindexer
User-Agent: YandexBot
User-Agent: Applebot
User-Agent: Claude-SearchBot
User-Agent: Applebot
User-Agent: AppleNewsBot
User-Agent: Bravebot
User-Agent: Googlebot
User-Agent: Googlebot-Image
User-Agent: Googlebot-News
User-Agent: Googlebot-Video
User-Agent: Bingbot
User-Agent: OAI-SearchBot
Disallow: /mail.php
Disallow: /search.php
Disallow: /search/*
Disallow: /trackback/

# Search Engines without local relevance
User-Agent: Baiduspider
User-Agent: Bytespider
User-Agent: Amazonbot
User-Agent: yacybot
User-Agent: SeznamBot
User-Agent: Seekport
User-Agent: coccocbot
User-Agent: Mojeek
User-Agent: Fleebs
User-Agent: Yeti
Disallow: /

# AI Training
User-Agent: Applebot-Extended
User-Agent: PetalBot
User-Agent: ClaudeBot
User-Agent: YouBot
User-Agent: GPTBot
User-Agent: PerplexityBot
User-Agent: Diffbot
User-Agent: GoogleAgent-Mariner
User-Agent: Googlebot-Extended
User-Agent: meta-externalagent
User-Agent: TimpiBot
User-Agent: img2dataset
User-Agent: iask.ai
User-Agent: VelenPublicWebCrawler
Disallow: /
Allow: /$
Allow: /specials/*
Allow: /ticker/*
Allow: /sonstiges/*
Allow: /top*
Allow: /aa-*
Allow: /plus*
Allow: /projekte*
Allow: /.well-known*


# Archives
User-Agent: archive.org_bot
User-Agent: arquivo-web-crawler
User-Agent: Heritrix
User-Agent: IABot
User-Agent: InternetArchive
Disallow: /

# Scraper
User-Agent: AhrefsBot #SEO
User-Agent: Ai2Bot #AI
User-Agent: Audisto-essential #SEO
User-Agent: AwarioBot #AI
User-Agent: BacklinkSpider #SEO
User-Agent: Barkrowler #SEO
User-Agent: Blackbox Exporter #monitoring
User-Agent: BLEXBot #SEO
User-Agent: BlogBeatbot #SEO
User-Agent: CrawlerBot #SEO
User-Agent: Dalvik
User-Agent: DataForSEO #SEO
User-Agent: Dotbot #AI
User-Agent: Google-CloudVertexBot
User-Agent: GoogleOther
User-Agent: GoogleOther-Video
User-Agent: KrawlerBot #SEO
User-Agent: LinkChecker #SEO
User-Agent: MeltwaterNews #listening
User-Agent: MJ12bot #SEO
User-Agent: Neticle Crawler #listening
User-Agent: Netvibes #listening
User-Agent: NoahBot #listening
User-Agent: Optimizer #SEO
User-Agent: Pinterestbot #Social
User-Agent: PlagAwareBot #plagiate
User-Agent: PressEngineBot #listening
User-Agent: PRTG Network Monitor #monitoring
User-Agent: Qwarrybot
User-Agent: RyteBot #SEO
User-Agent: SemrushBot #SEO
User-Agent: SemrushBot-BA #SEO
User-Agent: SemrushBot-EO #SEO
User-Agent: SemrushBot-ESI #SEO
User-Agent: SemrushBot-FT #SEO
User-Agent: SemrushBot-OCOB #SEO
User-Agent: SemrushBot-SI #SEO
User-Agent: SemrushBot-SWA #SEO
User-Agent: SentiBot #listening
User-Agent: SeobilityBot #SEO
User-Agent: SiteAuditBot #SEO
User-Agent: SplitSignalBot #SEO
User-Agent: TaranisAI #monitoring
User-Agent: trendictionbot #listening
User-Agent: Uptime-Kuma #monitoring
User-Agent: YandexMetrika
Disallow: /

Sitemap: https://www.golem.de/gsiteindex.xml

# Legal notice: golem.de expressly reserves the right to use its content for commercial text and data mining (§ 44 b UrhG).
# The use of robots or other automated means to access golem.de or collect or mine data without the express permission of golem.de is strictly prohibited.
# golem.de may, in its discretion, permit certain automated access to certain golem.de pages.
# If you would like to apply for permission to crawl golem.de, collect or use data, please email recht@golem.de
sitemap.xml 200 OK
Type Sitemap Index URLs 343 entries Valid XML Yes
Child Sitemaps:
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: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.golem.de/
301https://golem.de/

Preferred variant: www

HTTP → HTTPS

301http://www.golem.de/ → https://www.golem.de/

Consistent

A+
Domain Intelligence
golem.de
PASS
golem.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.
Domain expiry

Unknown

SSL certificate

109 days

Issued by DigiCert Inc

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2a00:13c8:f5::f:4b3d:148

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 2a00:13c8:f5::f:4b3d:148
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 138 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
37 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
32 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
35 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
139 ms
Total Time Total request time from DNS lookup through full response.
139 ms

Connection waterfall

DNS Lookup 37 ms TCP Connect 32 ms TLS Handshake 35 ms Server Processing 34 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback