Skip to content
https://muenchen.de

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 3 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

B
URL Variants
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
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.muenchen.de/
200https://muenchen.de/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://muenchen.de/ → https://muenchen.de/

Consistent

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

Certificate validity

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

Recommended actions

  • 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
4 A records, 47 ms lookup
PASS
4 A records, 47 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.66.216, 151.101.194.216, 151.101.130.216, 151.101.2.216
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns02e.muenchen.de, ns01e.muenchen.de, ns04e.muenchen.de
Info::
4 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: 47 ms
Got: 47 ms
A151.101.66.216, 151.101.194.216, 151.101.130.216, 151.101.2.216
AAAA—
CNAME—
NSns02e.muenchen.de, ns01e.muenchen.de, ns04e.muenchen.de
MX
10 c119-apb20-rz.muenchen.de
10 c119-k30-rz.muenchen.de
10 c118-k30-rz.muenchen.de
10 c118-apb20-rz.muenchen.de
TXT
SPF v=spf1 mx -all
hk0lol8s0t1i3dane5cgdjbgme
_snd2nvcbuy14grn8cnz3i022onllb26
cisco-ci-domain-verification=20c21e579e7e935cd3e7196cba7a9b9a39b6aecf3b24eafb881...
vt67fslhb5bpj73kv9l2kpqscb
apple-domain-verification=MNANb2lcdzz6d6SE
duo_sso_verification=l0uwhvzaIwFcrHAaoGFRCgJiX5fsCiuv9IxapkycYw5exwQ374bzPdp3QhJ...
cisco-ci-domain-verification=5030c92bf8abac49dd887044afeadf11e92869b8ecab91841f0...
_telesec-domain-validation=353728_2025-11-04_XqEy42Px0lkulF4ELkXjtEdbPENZAJ9y0TC...
tlliL0e0H0yBcddC3nrPiw4PUqoEIS5+i7+Xl1TTsF4=
adobe-idp-site-verification=dbeb15ad8215ac516675b24c31c517959f86d79f7be136450cb1...
successfactors-site-verification=NDk2Y2FlMGE0NzFhOTBiMjdkOWQ5ZDQzYzk1MTYwOGU3NjZ...
CAALookup not available with standard resolver
Resolved in 47 ms

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

https://muenchen.de

5 ms · HTTP/1.1

301

https://www.muenchen.de/

94 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://muenchen.de3015 msHTTP/1.1
2https://www.muenchen.de/20094 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 2858 URLs
PASS
robots.txt present, sitemap with 2858 URLs
Info::
robots.txt is present
Got: 1740 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2858 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 1740 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
#
# robots.txt - local
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used:    http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html

User-agent: *
# CSS, JS, Images
Allow: /core/*.css$
Allow: /core/*.css?
Allow: /core/*.js$
Allow: /core/*.js?
Allow: /core/*.gif
Allow: /core/*.jpg
Allow: /core/*.jpeg
Allow: /core/*.png
Allow: /core/*.svg
Allow: /profiles/*.css$
Allow: /profiles/*.css?
Allow: /profiles/*.js$
Allow: /profiles/*.js?
Allow: /profiles/*.gif
Allow: /profiles/*.jpg
Allow: /profiles/*.jpeg
Allow: /profiles/*.png
Allow: /profiles/*.svg
# Directories
Disallow: /core/
Disallow: /profiles/
# Files
Disallow: /README.txt
Disallow: /web.config
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register
Disallow: /user/password
Disallow: /user/login
Disallow: /user/logout
Disallow: /media/oembed
Disallow: /*/media/oembed
# Paths (no clean URLs)
Disallow: /index.php/admin/
Disallow: /index.php/comment/reply/
Disallow: /index.php/filter/tips
Disallow: /index.php/node/add/
Disallow: /index.php/search/
Disallow: /index.php/user/password
Disallow: /index.php/user/register
Disallow: /index.php/user/login
Disallow: /index.php/user/logout
Disallow: /index.php/media/oembed
Disallow: /index.php/*/media/oembed
Disallow: /*&date-start=*
sitemap.xml 200 OK
Type URL Set URLs 2858 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
muenchen.de — hosted on Fastly
PASS
muenchen.de — hosted on Fastly
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: Fastly
Got: AS54113
Domain expiry

Unknown

SSL certificate

61 days

Issued by Let's Encrypt

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

151.101.194.216

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 151.101.194.216
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
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 51 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
46 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
0 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
3 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
51 ms
Total Time Total request time from DNS lookup through full response.
51 ms

Connection waterfall

DNS Lookup 46 ms TCP Connect 0 ms TLS Handshake 3 ms Server Processing 1 ms Content Transfer 0 ms
A+
CDN & Delivery
Fastly (HIT, HIT)
PASS
Fastly (HIT, HIT)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-fra-eddf8230210-FRA, cache-toj-leto2350076-TOJ
Info::
CDN cache status: HIT, HIT
CDN Detected: Fastly
Provider Fastly Cache Status HIT, HIT Evidence x-served-by: cache-fra-eddf8230210-FRA, cache-toj-leto2350076-TOJ
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback