Skip to content
https://hillegom.nl

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
0
REVIEW
8
PASS
9
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
9 PASS 8 REVIEW
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 31.7.1.92 does not match any cert SAN: hlt.acato.cloud
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 2a03:9700:8000:1::92 does not match any cert SAN: hlt.acato.cloud
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
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 403 Expected: 301 redirect to HTTPS

www / non-www

403https://www.hillegom.nl/
200https://hillegom.nl/

HTTP → HTTPS

403http://hillegom.nl/

HTTP version does not redirect to HTTPS

B
HTTP Probe Timing
Total 905 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
54 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
27 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
31 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
905 ms
Total Time Total request time from DNS lookup through full response.
906 ms

Connection waterfall

DNS Lookup 54 ms TCP Connect 27 ms TLS Handshake 31 ms Server Processing 792 ms Content Transfer 1 ms
B
TLS Certificate Expiry & Recommendations
127 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

127
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 OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
C
CDN & Delivery
Action
Assets on CDN77 (host cdn-eu.readspeaker.com, 3 assets); document served directly from origin
REVIEW
Assets on CDN77 (host cdn-eu.readspeaker.com, 3 assets); document served directly from origin
Warning::
Document not behind existing CDN (CDN77 serves the assets)
The page's subresources are delivered by CDN77 (cdn-eu.readspeaker.com, 3 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: delegation 1630983047.rsc.cdn77.org
Info::
Assets on CDN77: cdn-eu.readspeaker.com (assets: 3)
Got: delegation 1630983047.rsc.cdn77.org
Warning: Assets on a CDN, document is not: CDN77
Document origin not attributed

Asset hosts on a CDN

  • cdn-eu.readspeaker.com — CDN77 · assets: 3

Other asset hosts

  • virtuele-gemeente-assistent.nl — assets: 2 · below probe threshold
  • meldingen.hollandsmiddenveilig.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.
A+
DNS Records
1 A records, 54 ms lookup
PASS
1 A records, 54 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 31.7.1.92
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: 2a03:9700:8000:1::92
Info::
2 nameserver(s) configured
Got: ns01.windinternet.nl, ns02.windinternet.net
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 54 ms
Got: 54 ms
A31.7.1.92
AAAA2a03:9700:8000:1::92
CNAME—
NSns01.windinternet.nl, ns02.windinternet.net
MX
0 hillegom-nl.l-v1.mx.microsoft
TXT
v=NTA7516-1;startdate=2019-06;enddate=2029-09;provider=bastionic;ntamx=10 mx.bas...
_uindycfiuz63t6yiijgc38wzbs0jpfl
dpiU16E+QuYN4NWM0POlH0DG9RXv0vhgASFHABYucy0VyCnfLcOfjOJ89KlHTb3RALpJ/BE1WOFnTR6o...
MS=ms88810256
bastion365-domain-validation=cab2b3b2a6ec6
_cfj2zju9ap2fto5ssbiogrb53sexwft
_jqo1okumgpb12syitlvet6bw65jd7gs
apple-domain-verification=xr4Tq0m2rVrmpLjJ
SPF v=spf1 include:spf.hillegom.nl.eu-yohpdrgi.e1.dspf.app -all
brevo-code:3ff469f7d4862443a10fe4fd47070b3c
brI2hGfkK3Xema/ozXmefbAvtGdr7oGIuN4TUbwpo98=
CAALookup not available with standard resolver
Resolved in 54 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+
DNSSEC
Signed and validating
PASS
Signed and validating
Info::
DNSSEC fully signed and chain validates (RSASHA256)
A
Multi-Resolver DNS Speed
Mean 60ms across 3 resolvers (spread 26ms)
PASS
Mean 60ms across 3 resolvers (spread 26ms)
Info::
Cloudflare: 50ms
Got: 50ms via 1.1.1.1:53
Info::
Google: 56ms
Got: 56ms via 8.8.8.8:53
Info::
Quad9: 76ms
Got: 76ms via 9.9.9.9:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://hillegom.nl

https://hillegom.nl

625 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://hillegom.nl200625 msHTTP/1.1
A+
IPv6 Readiness
IPv6 reachable (30 ms)
PASS
IPv6 reachable (30 ms)
Info::
IPv6 is configured and reachable at 2a03:9700:8000:1::92
Got: 30 ms connect
IPv6 Ready
AAAA Records 2a03:9700:8000:1::92 Connection Reachable (30 ms)
A+
Crawlability
robots.txt present, sitemap with 11 URLs
PASS
robots.txt present, sitemap with 11 URLs
Info::
robots.txt is present
Got: 258 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 11 entries
Info::
Sitemap index with 11 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 258 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Crawl-delay: 1
Disallow: /wp/wp-admin/
Allow: /wp/wp-admin/admin-ajax.php

# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://hillegom.nl/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
sitemap.xml 200 OK
Type Sitemap Index URLs 11 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
hillegom.nl — via The Registrar Company B.V., 28 years, 8 months old
PASS
hillegom.nl — via The Registrar Company B.V., 28 years, 8 months old
Info::
DNSSEC is enabled
Info::
Registrar: The Registrar Company B.V.
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

Unknown

SSL certificate

127 days

Issued by PerfectSSL

Domain age

28 years, 8 months

Registered August 3, 1998

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2a03:9700:8000:1::92

Registrar

The Registrar Company B.V.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar The Registrar Company B.V.
Created August 3, 1998 (28 years, 8 months ago)
Last Updated March 9, 2021
Name Servers ns01.windinternet.nl, ns02.windinternet.net
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 2a03:9700:8000:1::92
Data source: rdap (0.3s)

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+
Health Check Endpoint
Auth-protected health endpoint at https://hillegom.nl/health (HTTP 403)
PASS
Auth-protected health endpoint at https://hillegom.nl/health (HTTP 403)
Info::
Auth-protected health endpoint exposed at https://hillegom.nl/health
Got: https://hillegom.nl/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback