Skip to content
https://www.woensdrecht.nl

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
64
GRADE
D
FIX
2
REVIEW
11
PASS
3
INFO
1
Probed from Amsterdam, Netherlands
200 OK
Checks
17
3 PASS 11 REVIEW 2 FIX
F
Multi-Resolver DNS Speed
Action
All public resolvers failed to resolve the domain
FIX
All public resolvers failed to resolve the domain
Critical::
DNS resolution failed against all public resolvers
1.1.1.1, 8.8.8.8, and 9.9.9.9 all failed to resolve this domain. Almost always means the domain is delegated incorrectly, the authoritative servers are unreachable, or the resolution returned NXDOMAIN/SERVFAIL across the board.
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2001:678:264:4610::13, 2001:678:264:4611::13, 2001:678:264:4612::13
Info::
IPv6 connection error
Got: dial tcp6 [2001:678:264:4610::13]:443: connect: no route to host
IPv6 Misconfigured
AAAA Records 2001:678:264:4610::13, 2001:678:264:4611::13, 2001:678:264:4612::13 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

B
DNS Records
3 A records, 42 ms lookup
REVIEW
3 A records, 42 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 91.241.6.76, 91.241.6.156, 91.241.6.195
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2001:678:264:4610::13, 2001:678:264:4611::13, 2001:678:264:4612::13
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: woensdrecht001.simgroephosting04.nl
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 42 ms
Got: 42 ms
A91.241.6.76, 91.241.6.156, 91.241.6.195
AAAA2001:678:264:4610::13, 2001:678:264:4611::13, 2001:678:264:4612::13
CNAMEwoensdrecht001.simgroephosting04.nl
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 42 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

C
DNSSEC
Action
DNSSEC posture not checked
REVIEW
DNSSEC posture not checked
Info::
DNSSEC posture not checked
Could not query the validating resolver for DNSSEC status. Network or resolver outage.
C
CAA Records
Action
CAA posture not checked
REVIEW
CAA posture not checked
Info::
CAA records not checked
Could not query the resolver for CAA records. Network or resolver outage.
C
Reverse DNS
Action
0/6 IPs match cert SAN
REVIEW
0/6 IPs match cert SAN
Info::
PTR lookup failed for 91.241.6.76: lookup 91.241.6.76: Temporary failure in name resolution
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 91.241.6.156: lookup 91.241.6.156: Temporary failure in name resolution
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 91.241.6.195: lookup 91.241.6.195: i/o timeout
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2001:678:264:4610::13: lookup 2001:678:264:4610::13: i/o timeout
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2001:678:264:4611::13: lookup 2001:678:264:4611::13: i/o timeout
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2001:678:264:4612::13: lookup 2001:678:264:4612::13: i/o timeout
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 0 Expected: 301 redirect to HTTPS

www / non-www

200https://www.woensdrecht.nl/
https://woensdrecht.nl/

HTTP → HTTPS

http://www.woensdrecht.nl/

HTTP version does not redirect to HTTPS

C
TLS Certificate Expiry & Recommendations
Action
22 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

22
days left
0d 30d 60d 90d+
Renew soon — under 30 days remaining

Recommended actions

  • Renew certificate — 22 days remaining
  • 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
C
CDN & Delivery
Action
Assets on AWS CloudFront (host cuatro.sim-cdn.nl, 79 assets); document served directly from origin
REVIEW
Assets on AWS CloudFront (host cuatro.sim-cdn.nl, 79 assets); document served directly from origin
Warning::
Document not behind existing CDN (AWS CloudFront serves the assets)
The page's subresources are delivered by AWS CloudFront (cuatro.sim-cdn.nl, 79 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
Got: x-amz-cf-id: PgFUSQyiHnLM5hb_SRuZwfXZp-Jm6-rTvcfGQ8-ZLpBClA6oOWP2Kw==
Info::
Assets on AWS CloudFront: cuatro.sim-cdn.nl (assets: 79), cache Hit from cloudfront
Got: x-amz-cf-id: PgFUSQyiHnLM5hb_SRuZwfXZp-Jm6-rTvcfGQ8-ZLpBClA6oOWP2Kw==
Info::
Assets on AWS CloudFront: app.tolkie.nl (assets: 3), cache Hit from cloudfront
Got: x-amz-cf-id: 5QZctsWheyxcelLgXC5tlquCS4L4Ae5k8kHP9Sn09eqSuudL2Gmhmw==
Info::
Assets on CDN77: cdn-eu.readspeaker.com (assets: 3)
Got: delegation 1630983047.rsc.cdn77.org
Warning: Assets on a CDN, document is not: AWS CloudFront
Document origin not attributed

Asset hosts on a CDN

  • cuatro.sim-cdn.nl — AWS CloudFront · assets: 79 · Cache Status: Hit from cloudfront
  • app.tolkie.nl — AWS CloudFront · assets: 3 · Cache Status: Hit from cloudfront
  • cdn-eu.readspeaker.com — CDN77 · assets: 3

Other asset hosts

  • woensdrecht.logging.simanalytics.nl — assets: 3 · AWS
  • fonts.bunny.net — assets: 2 · below probe threshold
  • cb.vrmwb.nl — assets: 1 · below probe threshold
  • www.vrmwb.nl — assets: 1 · below probe threshold

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

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: connection error, /health: connection error, /healthz: connection error, /ping: connection error, /status: connection error.
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.woensdrecht.nl

https://www.woensdrecht.nl

153 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.woensdrecht.nl200153 msHTTP/1.1
A+
HTTP Probe Timing
Total 182 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
32 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
16 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
22 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
127 ms
Total Time Total request time from DNS lookup through full response.
182 ms

Connection waterfall

DNS Lookup 32 ms TCP Connect 16 ms TLS Handshake 22 ms Server Processing 57 ms Content Transfer 55 ms
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback