Skip to content
https://fetish4all.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
1
REVIEW
7
PASS
9
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
9 PASS 7 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
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).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 185.104.29.50 does not match any cert SAN: web0102.zxcs.nl
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 2a06:2ec0:1::102 does not match any cert SAN: web0102.zxcs.nl
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
B
TLS Certificate Expiry & Recommendations
64 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

64
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
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: 500, /health: 500, /healthz: 500, /ping: 500, /status: 500.
A+
DNS Records
1 A records, 56 ms lookup
PASS
1 A records, 56 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 185.104.29.50
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: 2a06:2ec0:1::102
Info::
3 nameserver(s) configured
Got: ns.zxcs.be, ns.zxcs.eu, ns.zxcs.nl
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 56 ms
Got: 56 ms
A185.104.29.50
AAAA2a06:2ec0:1::102
CNAME—
NSns.zxcs.be, ns.zxcs.eu, ns.zxcs.nl
MX
10 mail.fetish4all.com
TXT
SPF v=spf1 a mx ip4:185.104.29.50 ip6:2a06:2ec0:1:0:0:0:0:102 include:filter-out.zxc...
google-site-verification=ApDXPaLmaRA2eg4WqHQUkUEFTgVrWmUPZRVlM7ZuFB4
yandex-verification: 3ec4ce0ff3c48a97
CAALookup not available with standard resolver
Resolved in 56 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+
Multi-Resolver DNS Speed
Mean 26ms across 3 resolvers (spread 26ms)
PASS
Mean 26ms across 3 resolvers (spread 26ms)
Info::
Quad9: 17ms
Got: 17ms via 9.9.9.9:53
Info::
Google: 20ms
Got: 20ms via 8.8.8.8:53
Info::
Cloudflare: 43ms
Got: 43ms via 1.1.1.1:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://fetish4all.com

https://fetish4all.com

154 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://fetish4all.com200154 msHTTP/1.1Apache
A+
IPv6 Readiness
IPv6 reachable (30 ms)
PASS
IPv6 reachable (30 ms)
Info::
IPv6 is configured and reachable at 2a06:2ec0:1::102
Got: 30 ms connect
IPv6 Ready
AAAA Records 2a06:2ec0:1::102 Connection Reachable (30 ms)
A+
Crawlability
robots.txt present, sitemap with 44 URLs
PASS
robots.txt present, sitemap with 44 URLs
Info::
robots.txt is present
Got: 250 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 44 entries
Info::
Sitemap index with 44 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 250 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
Sitemap: https://fetish4all.com/sitemap_index.xml
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

# SHIELD::START
# ------------------------
User-agent: *
Disallow: /icwp-wpsf-link-cheese/
# ------------------------
# SHIELD::END
sitemap.xml 200 OK
Type Sitemap Index URLs 44 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

500https://www.fetish4all.com/
200https://fetish4all.com/

HTTP → HTTPS

301http://fetish4all.com/ → https://fetish4all.com/

Consistent

A+
Domain Intelligence
fetish4all.com — via Key-Systems GmbH, 7 years, 7 months old
PASS
fetish4all.com — via Key-Systems GmbH, 7 years, 7 months old
Info::
Domain registered until Jan 26, 2027 (5 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Key-Systems GmbH
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

162 days

January 26, 2027

SSL certificate

64 days

Issued by Let's Encrypt

Domain age

7 years, 7 months

Registered January 26, 2019

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a06:2ec0:1::102

Registrar

Key-Systems GmbH

Unlocked 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Key-Systems GmbH
Created January 26, 2019 (7 years, 7 months ago)
Expires January 26, 2027 (5 months)
Last Updated January 27, 2026
Name Servers ns.zxcs.be, ns.zxcs.eu, ns.zxcs.nl
DNSSEC Not enabled
Hosting
IP Address 2a06:2ec0:1::102
Data source: rdap (0.2s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

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 206 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.
41 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
175 ms
Total Time Total request time from DNS lookup through full response.
206 ms

Connection waterfall

DNS Lookup 42 ms TCP Connect 31 ms TLS Handshake 41 ms Server Processing 62 ms Content Transfer 31 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback