Skip to content
https://rijksmuseum.nl

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
5 PASS 2 REVIEW 2 FIX
D
Redirect Chain
Action
2 redirect(s), 3058 ms total
FIX
2 redirect(s), 3058 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.rijksmuseum.nl/
Warning::
Redirect overhead: 3058 ms total
Got: 3058 ms

https://rijksmuseum.nl

814 ms · HTTP/1.1

301

https://www.rijksmuseum.nl/

849 ms · HTTP/1.1

302

https://www.rijksmuseum.nl/nl

1394 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://rijksmuseum.nl301814 msHTTP/1.1Microsoft-IIS/10.0
2https://www.rijksmuseum.nl/302849 msHTTP/1.1
3https://www.rijksmuseum.nl/nl2001394 msHTTP/1.1

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

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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.

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
TLS Certificate Expiry & Recommendations
124 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A
DNS Records
1 A records, 918 ms lookup
PASS
1 A records, 918 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 20.50.2.49
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns1.zurich.surf.net, ns1.surfnet.nl, ns2.surfnet.nl, ns3.surfnet.nl
Info::
1 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
Warning::
DNS resolution is slow (918 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 918 ms
A20.50.2.49
AAAA—
CNAME—
NSns1.zurich.surf.net, ns1.surfnet.nl, ns2.surfnet.nl, ns3.surfnet.nl
MX
10 rijksmuseum-nl.mail.protection.outlook.com
TXT
HARICA-MJu4XdokojjQfcxxHGr
HARICA-WGc8iM5TJO2obnrbUVY
HARICA-anvfIJTcJoNcMjYgQp2
d365mktkey=1g2v57ske0n58fc3wvogj9zno
d365mktkey=6kvzzqfxnmbmwazm9tmf3xad3
apple-domain-verification=NshxooTSslDJNUcL
d365mktkey=eOlDKHIQjqp3d0o1Z68vxkqEvUEOGLtyd4H74VGaFucx
miro-verification=fda7e712c9d77ee612e598b448be6865345c82cf
facebook-domain-verification=3ga93f8qkrsqlnq7bf7g35v9odn2t4
5705203DD710C48C167466E90176AD51FC41AB6934DA3F88C53804148B3E0BFE
google-site-verification=PtYJpvw9iDYKZPWJGcLYAOL0EUrXe7qxe6OEHU57vSk
Hx4T7ENp7IdCRTaJLFua4Z2A3LZz94/y3gwOs2w7WojvDPg3IDoAhTerilZS/bpPWpXcxTNiCwAVKczW...
MItPhviB18a/XeFh4ccmBQ54m/fCHifxfWrDkeOUdgC+Ob/mpdFYpj+KemX7EICYKK1NypX2sbMPzF0l...
SPF v=spf1 ip4:192.87.126.0/28 ip4:192.87.126.34 ip4:81.246.113.50 ip4:149.72.46.57 ...
CAALookup not available with standard resolver
Resolved in 918 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

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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Crawlability
robots.txt present, sitemap with 58 URLs
PASS
robots.txt present, sitemap with 58 URLs
Info::
robots.txt is present
Got: 143 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 58 entries
Info::
Sitemap index with 58 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 143 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Allow: /

Disallow: /nl/collectie/zoeken?*

Disallow: /en/collection/search?*


Sitemap: https://www.rijksmuseum.nl/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 58 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::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

302https://www.rijksmuseum.nl/
200https://rijksmuseum.nl/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
rijksmuseum.nl — via SURF B.V., 30 years, 11 months old, hosted on Microsoft Azure
PASS
rijksmuseum.nl — via SURF B.V., 30 years, 11 months old, hosted on Microsoft Azure
Info::
DNSSEC is enabled
Info::
Registrar: SURF 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.
Info::
Hosting: Microsoft Azure
Got: AS8075
Domain expiry

Unknown

SSL certificate

124 days

Issued by DigiCert Inc

Domain age

30 years, 11 months

Registered October 2, 1995

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8075

20.50.2.49

Registrar

SURF B.V.

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 SURF B.V.
Created October 2, 1995 (30 years, 11 months ago)
Last Updated March 31, 2026
Name Servers ns2.surfnet.nl, ns3.surfnet.nl, ns1.surfnet.nl, ns1.zurich.surf.net
DNSSEC Enabled
Registrant Stichting het Rijksmuseum Amsterdam
Hosting
IP Address 20.50.2.49
ASN AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)
Provider Microsoft Azure
Data source: rdap (1.0s)

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

Connection waterfall

DNS Lookup 156 ms TCP Connect 153 ms TLS Handshake 331 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