Skip to content
https://berlin.de

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
308 Permanent Redirect
Checks
9
5 PASS 3 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
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 24 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

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 24 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow:
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

C
URL Variants
Action
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.berlin.de/
200https://berlin.de/

Inconsistent — duplicate content risk

HTTP → HTTPS

308http://berlin.de/ → https://berlin.de/

Use 301 (permanent) instead of 302 (temporary)

C
TLS Certificate Expiry & Recommendations
Action
21 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

21
days left
0d 30d 60d 90d+
Renew soon — under 30 days remaining

Recommended actions

  • Renew certificate — 21 days remaining
  • 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, 36 ms lookup
PASS
1 A records, 36 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 109.68.230.145
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::393:8a4d:2
Info::
4 nameserver(s) configured
Got: ns-391.awsdns-48.com, ns-931.awsdns-52.net, ns-1719.awsdns-22.co.uk, ns-1460.awsdns-54.org
Info::
2 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: 36 ms
Got: 36 ms
A109.68.230.145
AAAA2a00:13c8:f5::393:8a4d:2
CNAME—
NSns-391.awsdns-48.com, ns-931.awsdns-52.net, ns-1719.awsdns-22.co.uk, ns-1460.awsdns-54.org
MX
10 mailin.berlin.de
50 secondary.snafu.de
TXT
SPF v=spf1 mx a:service.berlinonline.de ip6:2a01:4f8:c01f:e7::1 ip6:2a01:4f8:c01f:e7...
abuseipdb-verification=LfrKgDpN
google-site-verification=tMQO2I0rVdhM-PmlH9jbp5sr8XzeZyAmnafwFKs2kgE
kctmddpdsfra04p0iiqn0a2ct
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

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
1 redirect(s), 258 ms total
PASS
1 redirect(s), 258 ms total
Info::
Single redirect
Got: https://berlin.de → https://www.berlin.de/ (308)
Info::
WWW normalization redirect

https://berlin.de

110 ms · HTTP/1.1

308

https://www.berlin.de/

148 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://berlin.de308110 msHTTP/1.1
2https://www.berlin.de/200148 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (33 ms)
PASS
IPv6 reachable (33 ms)
Info::
IPv6 is configured and reachable at 2a00:13c8:f5::393:8a4d:2
Got: 33 ms connect
IPv6 Ready
AAAA Records 2a00:13c8:f5::393:8a4d:2 Connection Reachable (33 ms)
A+
Domain Intelligence
berlin.de
PASS
berlin.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

21 days

Issued by Let's Encrypt

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2a00:13c8:f5::393:8a4d:2

Registrar

Registrar unknown

Unlocked Name servers unknown
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the TLS certificate or verify auto-renewal is working
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar
Hosting
IP Address 2a00:13c8:f5::393:8a4d:2
Data source: whois (0.4s)

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 145 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
32 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.
145 ms
Total Time Total request time from DNS lookup through full response.
145 ms

Connection waterfall

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