Skip to content
https://vu.nl

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from New York, United Stated
302 Found
Checks
9
6 PASS 2 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.

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
233 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

233
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
A
DNS Records
1 A records, 560 ms lookup
PASS
1 A records, 560 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 52.232.69.102
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: new-ns1.vu.nl, new-ns2.vu.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 (560 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 560 ms
A52.232.69.102
AAAA
CNAME
NSnew-ns1.vu.nl, new-ns2.vu.nl
MX
0 vu-nl.mail.protection.outlook.com
TXT
MS=ms11195063
MS=ms33278211
Phone: +31 20 5985385
HARICA-2AQWWJAqj5VSqkz0rOX
Vrije Universiteit Amsterdam
ZOOM_verify_gOlFjB0bTXauhCZZfZ0SZA
935e51b8-957b-486c-bca0-52db87534023
B8RKMH5ZV1ICEXRNIUXA04C1D4UXWARTPQE3T8PTL
apple-domain-verification=CQxBk5H2cH0MlovF
HO5Hae8DJUssBXMJPxF8SuoTVyO4suOdM/31NLC0WwA=
Address: De Boelelaan 1105, 1081 HV Amsterdam
jamf-site-verification=mTKqAuu3KFc2rfzUgyBWng
bw=JD9O8B5T3N8rye1GFjQP5tlEtsH7SuVOiTWPxSNk67Kr
facebook-domain-verification=z5lo4vme7tj7rz0rkrjeyw3ficdkrt
google-site-verification=5wBwCtzHALiL0eFj_8LfcLtC9A0pwqF8ChcfKHGWeUg
cEePUaAdUpgbDwN8y+iChaM5q/fmwZ98byweLOwQQTzlfZ7ZqiRmUZy9plWcraR+SpUS7soZ99JhnT3u...
atlassian-domain-verification=4DKZByaje8L/OfqPKIBr9eFCxXWL7x17aQeSAH5OE0dv32q8PX...
successfactors-site-verification=NDVmYTkwNzVjMjQ3NDgwYTRiNTZiYjM4YWY0MjUwNjE4NDE...
SPF v=spf1 include:_spf.vu.nl include:spf.protection.outlook.com include:_spf.x-com...
CAALookup not available with standard resolver
Resolved in 560 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
Redirect Chain
1 redirect(s), 699 ms total
PASS
1 redirect(s), 699 ms total
Info::
Single redirect
Got: https://vu.nl → https://vu.nl/nl (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://vu.nl
Info::
Redirect overhead: 699 ms total
Got: 699 ms

https://vu.nl

335 ms · HTTP/1.1

302

https://vu.nl/nl

365 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://vu.nl302335 msHTTP/1.1
2https://vu.nl/nl200365 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

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

A+
Crawlability
robots.txt present, sitemap with 23445 URLs
PASS
robots.txt present, sitemap with 23445 URLs
Info::
robots.txt is present
Got: 209 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 23445 entries
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 209 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
# Sharing knowledge is the most fundamental act of friendship. Because it is a way you can give something without loosing something.
User-agent: *
Disallow: /nl/mijn-studiekeuze/
Disallow: /en/my-studychoice/

sitemap.xml 200 OK
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)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

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

Preferred variant: non-www

HTTP → HTTPS

302http://vu.nl/ https://vu.nl/nl

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
vu.nl — via SURF B.V., 37 years, 8 months old, hosted on Microsoft Azure
PASS
vu.nl — via SURF B.V., 37 years, 8 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

233 days

Issued by Hellenic Academic and Research Institutions CA

Domain age

37 years, 8 months

Registered February 15, 1989

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8075

52.232.69.102

Registrar

SURF 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 SURF B.V.
Created February 15, 1989 (37 years, 8 months ago)
Last Updated January 5, 2026
Name Servers new-ns1.vu.nl, new-ns2.vu.nl
DNSSEC Enabled
Registrant Vrije Universiteit
Hosting
IP Address 52.232.69.102
ASN AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)
Provider Microsoft Azure
Data source: rdap (0.5s)

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

Connection waterfall

DNS Lookup 377 ms TCP Connect 78 ms TLS Handshake 84 ms Server Processing 79 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