Skip to content
https://golem.de

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
94
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 2 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
Redirect Chain
2 redirect(s), 385 ms total
REVIEW
2 redirect(s), 385 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.golem.de/

https://golem.de

110 ms · HTTP/1.1

301

https://www.golem.de/

139 ms · HTTP/1.1

302

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

135 ms · HTTP/1.1 FINAL

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

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

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

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

Certificate validity

135
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
A+
DNS Records
1 A records, 37 ms lookup
PASS
1 A records, 37 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::
4 nameserver(s) configured
Got: ns03.syseleven.de, ns02.syseleven.de, ns04.syseleven.de, ns01.syseleven.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
Info::
DNS resolution time: 37 ms
Got: 37 ms
A77.247.84.129
AAAA2a00:13c8:f5::f:4b3d:148
CNAME—
NSns03.syseleven.de, ns02.syseleven.de, ns04.syseleven.de, ns01.syseleven.de
MX
10 golem-de.mail.protection.outlook.com
TXT
google-site-verification=bW6sIv8blPCQxUCXt-y4yHr8NOqri7V0EWMxZ_Hmy34
google-site-verification=NYiBavW3CzXq_9CN4JS2-9ZVq1CAt8JGkH18usv2HY0
MS=ms18431984
brevo-code:0ac55cd98d87cec34c66d7eb881d56e0
SPF v=spf1 mx ip4:176.74.59.0/24 ip4:217.92.47.108 ip4:37.123.109.247 ip4:37.49.159....
google-site-verification=DCizdjgG41vs-LfgrJgxAmFOI2yj9P8AiN_sQR1Yd_w
atlassian-domain-verification=cQUIOe8hW6yNudUwjkJedocZb4G5a/OGPj4ow15Zxi6T9gID71...
google-site-verification=KmHYftRRSebpdfmwpmafDBb2ELj0ws7QexueFxL_wjk
amazonses:Ic+XRucPH5ALW2hkrBJX8DMn9Fv/dV1ZZEHZuL3hf3Q=
openai-domain-verification=dv-Z6nVxvSSGYgGaXRy6gpYO3AZ
CAALookup not available with standard resolver
Resolved in 37 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+
IPv6 Readiness
IPv6 reachable (33 ms)
PASS
IPv6 reachable (33 ms)
Info::
IPv6 is configured and reachable at 2a00:13c8:f5::f:4b3d:148
Got: 33 ms connect
IPv6 Ready
AAAA Records 2a00:13c8:f5::f:4b3d:148 Connection Reachable (33 ms)
A+
Crawlability
robots.txt present, sitemap with 342 URLs
PASS
robots.txt present, sitemap with 342 URLs
Info::
robots.txt is present
Got: 3647 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 342 entries
Info::
Sitemap index with 342 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 3647 B Sitemaps referenced 1 User-agents Blackbox Exporter #monitoring, Dalvik, Google-CloudVertexBot, SemrushBot-SI #SEO, SplitSignalBot #SEO, yacybot, KrawlerBot #SEO, TaranisAI #monitoring, DuckDuckBot, Qwantbot-news, Claude-SearchBot, iask.ai, GoogleOther-Video, SemrushBot-EO #SEO, trendictionbot #listening, img2dataset, AhrefsBot #SEO, Neticle Crawler #listening, PRTG Network Monitor #monitoring, SemrushBot-BA #SEO, OAI-SearchBot, Amazonbot, PetalBot, archive.org_bot, Heritrix, InternetArchive, CrawlerBot #SEO, Dotbot #AI, Applebot, Googlebot-Image, Applebot-Extended, SemrushBot-OCOB #SEO, BLEXBot #SEO, Netvibes #listening, Optimizer #SEO, Qwantbot, VelenPublicWebCrawler, Barkrowler #SEO, NoahBot #listening, Qwarrybot, SentiBot #listening, YandexMetrika, Bingbot, Mojeek, Bravebot, Yeti, Diffbot, BacklinkSpider #SEO, DataForSEO #SEO, LinkChecker #SEO, Uptime-Kuma #monitoring, *, Googlebot-Video, Bytespider, SeznamBot, Fleebs, arquivo-web-crawler, MeltwaterNews #listening, YandexBot, Baiduspider, GPTBot, Audisto-essential #SEO, GoogleOther, Pinterestbot #Social, SemrushBot-ESI #SEO, ClaudeBot, BlogBeatbot #SEO, MJ12bot #SEO, PressEngineBot #listening, SiteAuditBot #SEO, YandexImages, AppleNewsBot, Seekport, meta-externalagent, IABot, Ai2Bot #AI, SemrushBot #SEO, SemrushBot-FT #SEO, coccocbot, meta-webindexer, Googlebot, PerplexityBot, Googlebot-Extended, PlagAwareBot #plagiate, SeobilityBot #SEO, slurp, DuckDuckGo, YandexMobileBot, Googlebot-News, YouBot, AwarioBot #AI, RyteBot #SEO, SemrushBot-SWA #SEO, GoogleAgent-Mariner, TimpiBot 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 342 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: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

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

Preferred variant: non-www

HTTP → HTTPS

301http://golem.de/ → https://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

135 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.
34 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
33 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
36 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
138 ms
Total Time Total request time from DNS lookup through full response.
138 ms

Connection waterfall

DNS Lookup 34 ms TCP Connect 33 ms TLS Handshake 36 ms Server Processing 36 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