Skip to content
https://filipnet.de

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
1
REVIEW
7
PASS
9
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
9 PASS 7 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN (document or assets)
FIX
No CDN (document or assets)
Warning::
No CDN (document or assets)
Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN (document or assets)

Consider using a CDN to improve global delivery speed and reduce origin load.

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
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 redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.filipnet.de/
200https://filipnet.de/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://filipnet.de/ → https://www.filipnet.de/

Consistent

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
1 A records, 45 ms lookup
PASS
1 A records, 45 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 185.207.106.71
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: nsc0.schlundtech.de, nsa0.schlundtech.de, nsd0.schlundtech.de, nsb0.schlundtech.de
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 45 ms
Got: 45 ms
A185.207.106.71
AAAA—
CNAME—
NSnsc0.schlundtech.de, nsa0.schlundtech.de, nsd0.schlundtech.de, nsb0.schlundtech.de
MX
10 vps03.filipnet.de
TXT
SPF v=spf1 a:vps03.filipnet.de ip4:46.38.235.172 ip6:2a03:4000:2:3c1:436:90ff:fee7:b...
google-site-verification=U9e9woOEE95zdXFHne9AO_D-w-Cl_rxaf3MYVUOVKrw
CAALookup not available with standard resolver
Resolved in 45 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

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
CAA Records
issue: letsencrypt.org | issuewild: letsencrypt.org | iodef configured
PASS
issue: letsencrypt.org | issuewild: letsencrypt.org | iodef configured
Info::
CAA issue tag present — authorized CA(s): letsencrypt.org
Info::
CAA iodef tag present (failed-issuance notifications enabled)
A+
Reverse DNS
1/1 IPs match cert SAN
PASS
1/1 IPs match cert SAN
Info::
PTR for 185.207.106.71 matches certificate SAN: lb01.filipnet.de
A+
Multi-Resolver DNS Speed
Mean 37ms across 3 resolvers (spread 18ms)
PASS
Mean 37ms across 3 resolvers (spread 18ms)
Info::
Google: 26ms
Got: 26ms via 8.8.8.8:53
Info::
Quad9: 43ms
Got: 43ms via 9.9.9.9:53
Info::
Cloudflare: 44ms
Got: 44ms via 1.1.1.1:53
A
Redirect Chain
1 redirect(s), 742 ms total
PASS
1 redirect(s), 742 ms total
Info::
Single redirect
Got: https://filipnet.de → https://www.filipnet.de/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 742 ms total
Got: 742 ms

https://filipnet.de

143 ms · HTTP/1.1

301

https://www.filipnet.de/

599 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://filipnet.de301143 msHTTP/1.1Apache
2https://www.filipnet.de/200599 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 107 URLs
PASS
robots.txt present, sitemap with 107 URLs
Info::
robots.txt is present
Got: 113 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 107 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 113 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://www.filipnet.de/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 107 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
filipnet.de — hosted on netcup-AS - netcup GmbH, DE
PASS
filipnet.de — hosted on netcup-AS - netcup GmbH, 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: netcup-AS - netcup GmbH, DE
Got: AS197540
Domain expiry

Unknown

SSL certificate

52 days

Issued by Let's Encrypt

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

netcup-AS - netcup GmbH, DE

ASN AS197540

185.207.106.71

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 185.207.106.71
ASN AS197540 (netcup-AS - netcup GmbH, DE)
Provider netcup-AS - netcup GmbH, DE
Data source: whois (0.8s)

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

Connection waterfall

DNS Lookup 42 ms TCP Connect 31 ms TLS Handshake 38 ms Server Processing 82 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