Skip to content
https://mpg.de

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
79
GRADE
C
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 3 REVIEW 2 FIX
D
Redirect Chain
Action
2 redirect(s), 1779 ms total
FIX
2 redirect(s), 1779 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
Warning::
Redirect overhead: 1779 ms total
Got: 1779 ms

https://mpg.de

113 ms · HTTP/1.0

301

https://www.mpg.de/

759 ms · HTTP/1.1

301

https://www.mpg.de/de

908 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mpg.de301113 msHTTP/1.0BigIP
2https://www.mpg.de/301759 msHTTP/1.1Apache
3https://www.mpg.de/de200908 msHTTP/1.1Apache

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

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.

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
Crawlability
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 87 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt references sitemap

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

robots.txt 200 OK
Size 87 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# Generated by CMS-App (default)
User-agent: *
Sitemap: https://www.mpg.de/sitemap.xml

sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
TLS Certificate Expiry & Recommendations
199 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

199
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, 44 ms lookup
PASS
1 A records, 44 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 134.76.31.198
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: ns1.es.net, dns2.gwdg.de, dns1.gwdg.de, sat.mpcdf.mpg.de, dns3.gwdg.de
Info::
3 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: 44 ms
Got: 44 ms
A134.76.31.198
AAAA
CNAME
NSns1.es.net, dns2.gwdg.de, dns1.gwdg.de, sat.mpcdf.mpg.de, dns3.gwdg.de
MX
50 b1236.mx.srv.dfn.de
50 a1236.mx.srv.dfn.de
50 c1236.mx.srv.dfn.de
TXT
google-site-verification=XHSgSiW3S-oNc6utmVvWr_K-iNo1ZpYHGDMV1ev8txw
adobe-idp-site-verification=4efc5f4912ea5b60334e2704bb3eb956c5e7849e481abd33757f...
hibp-verify=dweb_0tywy72sz0avnp2yfrm5v1g9
zone-ownership-verification-4e95ba1562fe6b7d7fd5000d249ed3fefed9803b10aab281fb17...
SPF v=spf1 mx include:spf.gwdg.de include:spf.yve-tool.de ip4:155.56.221.13 ip4:155....
google-site-verification=dnSBuenbktdrWBa2AyYCTsb6kohTtitwQvtLHzFcXWM
MS=ms65105063
google-site-verification=_8HT2hqpeJwL__q-eYwM6eKubRP2nX8kFao2_IlfZOc
CAALookup not available with standard resolver
Resolved in 44 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+
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

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

Preferred variant: non-www

HTTP → HTTPS

301http://mpg.de/ https://mpg.de/

Consistent

A+
Domain Intelligence
mpg.de — hosted on GOENET, DE
PASS
mpg.de — hosted on GOENET, 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: GOENET, DE
Got: AS207592
Domain expiry

Unknown

SSL certificate

199 days

Issued by Hellenic Academic and Research Institutions CA

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

GOENET, DE

ASN AS207592

134.76.31.198

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 134.76.31.198
ASN AS207592 (GOENET, DE)
Provider GOENET, DE
Data source: whois (0.9s)

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 153 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
39 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
36 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
42 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
153 ms
Total Time Total request time from DNS lookup through full response.
153 ms

Connection waterfall

DNS Lookup 39 ms TCP Connect 36 ms TLS Handshake 42 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