Skip to content
https://www.pijnacker-nootdorp.nl

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
0
REVIEW
9
PASS
8
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
8 PASS 9 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/6 IPs match cert SAN
REVIEW
0/6 IPs match cert SAN
Info::
PTR for 31.7.6.87 does not match any cert SAN: customer-lb2.k8s.shockmedia.host
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 31.7.0.60 does not match any cert SAN: customer-lb1.k8s.shockmedia.host
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 185.144.224.28 does not match any cert SAN: customer-lb3.k8s.shockmedia.host
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::24 does not match any cert SAN: customer-lb2.k8s.shockmedia.host
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::23 does not match any cert SAN: customer-lb1.k8s.shockmedia.host
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::25 does not match any cert SAN: customer-lb3.k8s.shockmedia.host
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.
C
HTTP Probe Timing
Action
Total 1806 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
43 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.
37 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.77 s
Total Time Total request time from DNS lookup through full response.
1.81 s

Connection waterfall

DNS Lookup 43 ms TCP Connect 27 ms TLS Handshake 37 ms Server Processing 1.66 s Content Transfer 36 ms
B
TLS Certificate Expiry & Recommendations
35 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

35
days left
0d 30d 60d 90d+

Recommended actions

  • 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 AWS CloudFront (host app.tolkie.nl, 3 assets); document served directly from origin
REVIEW
Assets on AWS CloudFront (host app.tolkie.nl, 3 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 (app.tolkie.nl, 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: x-amz-cf-id: RL0R2lHMFbLZJyvSZyLD8X8Xn8I2ucdE-MPxLhRu6KW68fNIE3Xbrw==
Info::
Assets on AWS CloudFront: app.tolkie.nl (assets: 3), cache Hit from cloudfront
Got: x-amz-cf-id: RL0R2lHMFbLZJyvSZyLD8X8Xn8I2ucdE-MPxLhRu6KW68fNIE3Xbrw==
Warning: Assets on a CDN, document is not: AWS CloudFront
Document origin not attributed

Asset hosts on a CDN

  • app.tolkie.nl — AWS CloudFront · assets: 3 · Cache Status: Hit from cloudfront

Other asset hosts

  • openpub.pijnacker-nootdorp.nl — assets: 3 · not attributed
  • cdn.tolkie.nl — assets: 2 · below probe threshold
  • virtuele-gemeente-assistent.nl — assets: 2 · below probe threshold
  • kit.fontawesome.com — assets: 1 · below probe threshold
  • scripts.simpleanalyticscdn.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: connection error, /health: 404, /healthz: connection error, /ping: connection error, /status: connection error.
A
DNS Records
3 A records, 52 ms lookup
PASS
3 A records, 52 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 31.7.6.87, 31.7.0.60, 185.144.224.28
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2a03:9700:8000:1::24, 2a03:9700:8000:1::23, 2a03:9700:8000:1::25
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: 52 ms
Got: 52 ms
A31.7.6.87, 31.7.0.60, 185.144.224.28
AAAA2a03:9700:8000:1::24, 2a03:9700:8000:1::23, 2a03:9700:8000:1::25
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 52 ms

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 53ms across 3 resolvers (spread 58ms)
PASS
Mean 53ms across 3 resolvers (spread 58ms)
Info::
Google: 26ms
Got: 26ms via 8.8.8.8:53
Info::
Cloudflare: 51ms
Got: 51ms via 1.1.1.1:53
Info::
Quad9: 84ms
Got: 84ms 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.pijnacker-nootdorp.nl

https://www.pijnacker-nootdorp.nl

1221 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.pijnacker-nootdorp.nl2001221 msHTTP/1.1
A+
IPv6 Readiness
IPv6 reachable (28 ms)
PASS
IPv6 reachable (28 ms)
Info::
IPv6 is configured and reachable at 2a03:9700:8000:1::24, 2a03:9700:8000:1::23, 2a03:9700:8000:1::25
Got: 28 ms connect
IPv6 Ready
AAAA Records 2a03:9700:8000:1::24, 2a03:9700:8000:1::23, 2a03:9700:8000:1::25 Connection Reachable (28 ms)
A+
Crawlability
robots.txt present, sitemap with 6 URLs
PASS
robots.txt present, sitemap with 6 URLs
Info::
robots.txt is present
Got: 474 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 6 entries
Info::
Sitemap index with 6 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 474 B Sitemaps referenced 0 User-agents ichiro, PetalBot, Yeti, AhrefsBot, Baiduspider, Baiduspider-image, DotBot, MJ12bot, NaverBot, SEMrushBot, *, Baiduspider-video, MauiBot, moget, SeznamBot, sogou spider, Yandex, YoudaoBot Blocking No — crawling allowed
User-agent: *

Disallow: /wp-admin/

Allow: /wp-admin/admin-ajax.php


User-agent: AhrefsBot

User-agent: Baiduspider

User-agent: Baiduspider-video

User-agent: Baiduspider-image

User-agent: DotBot

User-agent: ichiro

User-agent: MauiBot

User-agent: MJ12bot

User-agent: moget

User-agent: NaverBot

User-agent: PetalBot

User-agent: SEMrushBot

User-agent: SeznamBot

User-agent: sogou spider

User-agent: Yandex

User-agent: Yeti

User-agent: YoudaoBot

Disallow: /
sitemap.xml 200 OK
Type Sitemap Index URLs 6 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 redirects to HTTPS permanently
Got: HTTP 308

www / non-www

200https://www.pijnacker-nootdorp.nl/
308https://pijnacker-nootdorp.nl/

HTTP → HTTPS

308http://www.pijnacker-nootdorp.nl/ → https://www.pijnacker-nootdorp.nl

Consistent

A+
Domain Intelligence
pijnacker-nootdorp.nl — via KPN B.V., 25 years, 9 months old
PASS
pijnacker-nootdorp.nl — via KPN B.V., 25 years, 9 months old
Info::
DNSSEC is enabled
Info::
Registrar: KPN 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

35 days

Issued by Sectigo Limited

Domain age

25 years, 9 months

Registered June 5, 2001

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2a03:9700:8000:1::23

Registrar

KPN 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 KPN B.V.
Created June 5, 2001 (25 years, 9 months ago)
Last Updated March 19, 2025
Name Servers ns11.kpn.net, ns1.kpn.net
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 2a03:9700:8000:1::23
Data source: rdap (0.2s)

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

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

Send Feedback