Skip to content
https://fes.de

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
78
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
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 0 Expected: 301 redirect to HTTPS

www / non-www

200https://www.fes.de/
200https://fes.de/

Inconsistent — duplicate content risk

HTTP → HTTPS

http://fes.de/

HTTP version does not redirect to HTTPS

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
1 redirect(s), 2434 ms total
REVIEW
1 redirect(s), 2434 ms total
Info::
Single redirect
Got: https://fes.de → https://www.fes.de/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 2434 ms total
Got: 2434 ms

https://fes.de

102 ms · HTTP/1.1

301

https://www.fes.de/

2332 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://fes.de301102 msHTTP/1.1nginx
2https://www.fes.de/2002332 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

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
TLS Certificate Expiry & Recommendations
233 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

233
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, 58 ms lookup
PASS
1 A records, 58 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 195.243.222.30
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns.fes.de, ns2.fes.de, pns.dtag.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: 58 ms
Got: 58 ms
A195.243.222.30
AAAA
CNAME
NSns.fes.de, ns2.fes.de, pns.dtag.de
MX
10 mail1.fes.de
TXT
_globalsign-domain-verification=g9678m9d289s32mqoo2jsicdbp
apple-domain-verification=N4bfRgMeT6JrrMA5
SPF v=spf1 ip4:195.243.222.11 ip4:195.243.222.33 ip4:195.243.222.75 ip4:195.243.222....
g9678m9d289s32mqoo2jsicdbp
CAALookup not available with standard resolver
Resolved in 58 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+
Crawlability
robots.txt present, sitemap with 17 URLs
PASS
robots.txt present, sitemap with 17 URLs
Info::
robots.txt is present
Got: 94 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 17 entries
Info::
Sitemap index with 17 child sitemaps
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 94 B Sitemaps referenced 0 User-agents *, Slurp Blocking No — crawling allowed
User-agent: *
Disallow: /archiv/SBZ-SPD/
Disallow: /MMWIP/
User-agent: Slurp
Crawl-delay: 0.5

A+
Domain Intelligence
fes.de — hosted on DTAG Internet service provider operations, DE
PASS
fes.de — hosted on DTAG Internet service provider operations, 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: DTAG Internet service provider operations, DE
Got: AS3320
Domain expiry

Unknown

SSL certificate

233 days

Issued by Sectigo Limited

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

DTAG Internet service provider operations, DE

ASN AS3320

195.243.222.30

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 195.243.222.30
ASN AS3320 (DTAG Internet service provider operations, DE)
Provider DTAG Internet service provider operations, DE
Data source: whois (0.7s)

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 149 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.
29 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
46 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
149 ms
Total Time Total request time from DNS lookup through full response.
150 ms

Connection waterfall

DNS Lookup 46 ms TCP Connect 29 ms TLS Handshake 46 ms Server Processing 29 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