Skip to content
https://www.bloemendaal.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
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.71.61.36 does not match any cert SAN: bldhmsprod03.cobytes.io
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:38a0:61:36::1 does not match any cert SAN: bldhmsprod03.cobytes.io
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
60 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

60
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

  • siteimproveanalytics.com — 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: 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.71.61.36
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:38a0:61:36::1
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: 45 ms
Got: 45 ms
A185.71.61.36
AAAA2a03:38a0:61:36::1
CNAME—
NS—
MX—
TXT—
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

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)

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 43ms across 3 resolvers (spread 48ms)
PASS
Mean 43ms across 3 resolvers (spread 48ms)
Info::
Google: 20ms
Got: 20ms via 8.8.8.8:53
Info::
Cloudflare: 41ms
Got: 41ms via 1.1.1.1:53
Info::
Quad9: 68ms
Got: 68ms 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://www.bloemendaal.nl

https://www.bloemendaal.nl

232 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.bloemendaal.nl200232 msHTTP/1.1nginx
A+
IPv6 Readiness
IPv6 reachable (26 ms)
PASS
IPv6 reachable (26 ms)
Info::
IPv6 is configured and reachable at 2a03:38a0:61:36::1
Got: 26 ms connect
IPv6 Ready
AAAA Records 2a03:38a0:61:36::1 Connection Reachable (26 ms)
A+
Crawlability
robots.txt present, sitemap with 424 URLs
PASS
robots.txt present, sitemap with 424 URLs
Info::
robots.txt is present
Got: 164 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 424 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 164 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Disallow: /waterloket/aanleg-duinrel-caprera
Disallow: /waterloket/piekberging-haarlemmermeer
Sitemap: https://www.bloemendaal.nl/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 424 entries Valid XML Yes
Sample URLs:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.bloemendaal.nl/
301https://bloemendaal.nl/

Preferred variant: www

HTTP → HTTPS

301http://www.bloemendaal.nl/ → https://www.bloemendaal.nl/

Consistent

A+
Domain Intelligence
bloemendaal.nl — via team.blue nl B.V., 28 years, 8 months old
PASS
bloemendaal.nl — via team.blue nl B.V., 28 years, 8 months old
Info::
DNSSEC is enabled
Info::
Registrar: team.blue nl 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

60 days

Issued by Let's Encrypt

Domain age

28 years, 8 months

Registered July 14, 1998

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2a03:38a0:61:36::1

Registrar

team.blue nl B.V.

Unlocked 3 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 team.blue nl B.V.
Created July 14, 1998 (28 years, 8 months ago)
Last Updated November 6, 2021
Name Servers ns2.transip.eu, ns0.transip.net, ns1.transip.nl
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 2a03:38a0:61:36::1
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+
HTTP Probe Timing
Total 288 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
48 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.
61 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
288 ms
Total Time Total request time from DNS lookup through full response.
289 ms

Connection waterfall

DNS Lookup 48 ms TCP Connect 26 ms TLS Handshake 61 ms Server Processing 154 ms Content Transfer 1 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback