Skip to content
https://rijksoverheid.nl

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Singapore, Singapore
301 Moved Permanently
Checks
9
5 PASS 3 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
Redirect Chain
1 redirect(s), 1126 ms total
REVIEW
1 redirect(s), 1126 ms total
Info::
Single redirect
Got: https://rijksoverheid.nl → https://www.rijksoverheid.nl/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1126 ms total
Got: 1126 ms

https://rijksoverheid.nl

643 ms · HTTP/1.1

301

https://www.rijksoverheid.nl/

484 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://rijksoverheid.nl301643 msHTTP/1.1nginx
2https://www.rijksoverheid.nl/200484 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

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.rijksoverheid.nl/
200https://rijksoverheid.nl/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://rijksoverheid.nl/ → https://rijksoverheid.nl/

Consistent

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

Certificate validity

85
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
A+
DNS Records
4 A records, 161 ms lookup
PASS
4 A records, 161 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 178.22.85.8, 178.22.85.9, 178.22.85.10, 178.22.85.11
Info::
Has 4 IPv6 (AAAA) record(s)
Got: 2a00:d00:3:2::3, 2a00:d00:3:2::4, 2a00:d00:3:2::5, 2a00:d00:3:2::6
Info::
4 nameserver(s) configured
Got: ns0.rijksoverheidnl.com, ns1.rijksoverheidnl.nl, ns2.rijksoverheidnl.eu, ns3.rijksoverheidnl.org
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 161 ms
Got: 161 ms
A178.22.85.8, 178.22.85.9, 178.22.85.10, 178.22.85.11
AAAA2a00:d00:3:2::3, 2a00:d00:3:2::4, 2a00:d00:3:2::5, 2a00:d00:3:2::6
CNAME—
NSns0.rijksoverheidnl.com, ns1.rijksoverheidnl.nl, ns2.rijksoverheidnl.eu, ns3.rijksoverheidnl.org
MX
10 mail2.ssonet.nl
10 mail.ssonet.nl
TXT
MS=ms19232603
SPF v=spf1 redirect=spf-a.ssonet.nl
cisco-ci-domain-verification=36a678bb84ff68a99eb62e168ea6e5e2de96a7e0dc884817eb1...
CAALookup not available with standard resolver
Resolved in 161 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
IPv6 Readiness
IPv6 reachable (236 ms)
PASS
IPv6 reachable (236 ms)
Info::
IPv6 is configured and reachable at 2a00:d00:3:2::3, 2a00:d00:3:2::4, 2a00:d00:3:2::5, 2a00:d00:3:2::6
Got: 236 ms connect
IPv6 Ready
AAAA Records 2a00:d00:3:2::3, 2a00:d00:3:2::4, 2a00:d00:3:2::5, 2a00:d00:3:2::6 Connection Reachable (236 ms)
A+
Crawlability
robots.txt present, sitemap with 5 URLs
PASS
robots.txt present, sitemap with 5 URLs
Info::
robots.txt is present
Got: 125 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 5 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 125 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed

User-agent: *
Disallow: /zoeken?

User-agent: *
Disallow: /error/*

Sitemap: https://www.rijksoverheid.nl/nieuws-sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 5 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
rijksoverheid.nl — via Rijksoverheid, 27 years, 2 months old
PASS
rijksoverheid.nl — via Rijksoverheid, 27 years, 2 months old
Info::
DNSSEC is enabled
Info::
Registrar: Rijksoverheid
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

85 days

Issued by DigiCert Ireland Limited

Domain age

27 years, 2 months

Registered July 6, 1999

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2a00:d00:3:2::4

Registrar

Rijksoverheid

Unlocked 4 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 Rijksoverheid
Created July 6, 1999 (27 years, 2 months ago)
Last Updated October 4, 2021
Name Servers ns1.rijksoverheidnl.nl, ns2.rijksoverheidnl.eu, ns3.rijksoverheidnl.org, ns0.rijksoverheidnl.com
DNSSEC Enabled
Registrant Rijksoverheid
Hosting
IP Address 2a00:d00:3:2::4
Data source: rdap (0.8s)

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 636 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
160 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
158 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
160 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
637 ms
Total Time Total request time from DNS lookup through full response.
637 ms

Connection waterfall

DNS Lookup 160 ms TCP Connect 158 ms TLS Handshake 160 ms Server Processing 158 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