Skip to content
https://vdwoude.eu

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
11
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
5 PASS 11 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/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 92.63.168.139 does not match any cert SAN: web-1028.yourhosting.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
Redirect Chain
2 redirect(s), 397 ms total
REVIEW
2 redirect(s), 397 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
HTTP to HTTPS redirect present
Info::
WWW normalization redirect
Warning::
2-hop chain could be reduced to 1 hop
Redirect directly from https://vdwoude.eu to https://www.vdwoude.eu/

https://vdwoude.eu

89 ms · HTTP/1.1

301

http://www.vdwoude.eu/

113 ms · HTTP/1.1

301

https://www.vdwoude.eu/

195 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://vdwoude.eu30189 msHTTP/1.1nginx
2http://www.vdwoude.eu/301113 msHTTP/1.1nginx
3https://www.vdwoude.eu/200195 msHTTP/1.1nginx

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

Redirect directly from https://vdwoude.eu to https://www.vdwoude.eu/

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

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, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 205 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

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 205 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /bbstat/

Disallow: /authy/

Disallow: /more/

Disallow: /termin/

Disallow: /stb-vdwt/

Disallow: /stb-tln/

Disallow: /stb-mu/

Disallow: /hwe/

Disallow: /vga/

Disallow: /vg-a/
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::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.vdwoude.eu/
200https://vdwoude.eu/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://vdwoude.eu/ → https://vdwoude.eu/

Consistent

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

Certificate validity

73
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
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, 68 ms lookup
PASS
1 A records, 68 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 92.63.168.139
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-g.dns.yourhosting.nl, ns-n.dns.yourhosting.eu, ns-f.dns.yourhosting.nu
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 68 ms
Got: 68 ms
A92.63.168.139
AAAA—
CNAME—
NSns-g.dns.yourhosting.nl, ns-n.dns.yourhosting.eu, ns-f.dns.yourhosting.nu
MX
10 primary.yourfilter.nl
20 fallback.yourfilter.nl
TXT
SPF v=spf1 mx a include:spf.alphamega.nl ~all
CAALookup not available with standard resolver
Resolved in 68 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 22ms across 3 resolvers (spread 38ms)
PASS
Mean 22ms across 3 resolvers (spread 38ms)
Info::
Quad9: 1ms
Got: 1ms via 9.9.9.9:53
Info::
Google: 27ms
Got: 27ms via 8.8.8.8:53
Info::
Cloudflare: 39ms
Got: 39ms via 1.1.1.1:53
A+
Domain Intelligence
vdwoude.eu — via Realtime Register B.V., hosted on CLDIN-NL Your Hosting B.V. part of Your.Online, NL
PASS
vdwoude.eu — via Realtime Register B.V., hosted on CLDIN-NL Your Hosting B.V. part of Your.Online, NL
Info::
Registrar: Realtime Register B.V.
Info::
Hosting: CLDIN-NL Your Hosting B.V. part of Your.Online, NL
Got: AS48635
Domain expiry

Unknown

SSL certificate

73 days

Issued by Let's Encrypt

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

CLDIN-NL Your Hosting B.V. part of Your.Online, NL

ASN AS48635

92.63.168.139

Registrar

Realtime Register B.V.

Lock status unknown 3 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Registrar Realtime Register B.V.
Name Servers ns-n.dns.yourhosting.eu, ns-f.dns.yourhosting.nu, ns-g.dns.yourhosting.nl
Registrant NOT DISCLOSED!
Hosting
IP Address 92.63.168.139
ASN AS48635 (CLDIN-NL Your Hosting B.V. part of Your.Online, NL)
Provider CLDIN-NL Your Hosting B.V. part of Your.Online, NL
Data source: whois (0.7s)
A+
HTTP Probe Timing
Total 124 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
33 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
26 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
28 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
125 ms
Total Time Total request time from DNS lookup through full response.
125 ms

Connection waterfall

DNS Lookup 33 ms TCP Connect 26 ms TLS Handshake 28 ms Server Processing 38 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