Skip to content
https://tue.nl

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
5
PASS
3
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
3 PASS 5 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
2 redirect(s), 336 ms total
REVIEW
2 redirect(s), 336 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

https://tue.nl

106 ms · HTTP/1.1

301

https://www.tue.nl/

90 ms · HTTP/1.1

301

https://www.tue.nl/en/

140 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://tue.nl301106 msHTTP/1.1
2https://www.tue.nl/30190 msHTTP/1.1
3https://www.tue.nl/en/200140 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

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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 712 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

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 712 B Sitemaps referenced 0 User-agents TeleportPro, wget, BlackWidow, *, Fasterfox, Teleport Blocking No — crawling allowed
User-Agent: *
Allow: /
Disallow: /t3lib/
Disallow: /typo3/
Disallow: /typo3conf/
Allow: /typo3conf/ext/*/Resources/Public/
Disallow: /typo3temp/
Allow: /typo3temp/compressor/
Allow: /typo3temp/pics/
Disallow: /storage/
Disallow: /search-results/*
Disallow: /*?no_cache=*
Disallow: /*?type=*
Disallow: /*?search=*
Disallow: /*?filter=*
Disallow: /*?filters=*
Disallow: /*?date=*

Disallow: /*?id=*
Crawl-delay: 3

# Sitemap: http://www.example.tld/sitemap.xml   # Your Sitemap
# Sitemap: http://www.example.tld/rss.xml       # Your RSS Feed

User-agent: Fasterfox
Disallow: /

User-agent: Teleport
Disallow: /

User-agent: TeleportPro
Disallow: /

User-agent: wget
Disallow: /

User-agent: BlackWidow
Disallow: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
HTTP Probe Timing
Total 1163 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
1.06 s
TCP Connect TCP Connect — time to establish a TCP connection to the server.
32 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
40 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.16 s
Total Time Total request time from DNS lookup through full response.
1.16 s

Connection waterfall

DNS Lookup 1.06 s TCP Connect 32 ms TLS Handshake 40 ms Server Processing 32 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
57 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

57
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, 1047 ms lookup
PASS
1 A records, 1047 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 131.155.10.135
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: ns01.tue.nl, ns02.tue.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 (1047 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 1047 ms
A131.155.10.135
AAAA—
CNAME—
NSns01.tue.nl, ns02.tue.nl
MX
10 tue-nl.mail.protection.outlook.com
TXT
P.O. Box 513, 5600 MB Eindhoven, The Netherlands
miro-verification=cb1958a2546dab9752639eeb5a07b1cf02ec18a8
mgverify=870f2f8187f4d172141d9f194ca8e343f25a36b8ebe3474e711a9d0e6eba4deb
globalsign-domain-verification=1F7EC979113CCDF8F244158D6DFF7947
google-site-verification=uNp_IVRt-7BLrpDzH925tElqmPLaeMVrFBV-MTNizv4
atlassian-domain-verification=EATjeWp2TWSpBt8CIt5ngmWgUCL58gs8ZYa9LUdUS4IiMHmeJi...
google-site-verification=WwQlrCFBbFYz9HaIZTCskfrONfrROlnfabGixoqwyS0
autodesk-domain-verification=p53xRNeOV9HPWzWd2l2t
SPF v=spf1 ip4:167.89.63.218 ip4:185.138.80.117 include:spfdefault.mail.tue.nl inclu...
facebook-domain-verification=eyg9tk0dlzfngb7spof8kirgsjye06
Eindhoven University of Technology
MS=58573ACBE8201AC4B395EF00A745C38DB1DD57FA
adobe-idp-site-verification=8d48631e0b4d87e4d1c6f0d04bc8c5b8106bfcdb3cfad0f0a2be...
anthropic-domain-verification-mdd659=5GXFiqI1LUZ2Qx559qlWCEU4x
HARICA-dzf3wGHrp8YxKUnknJg
mentimeter-aa1b69ac-305e-466e-bcd6-aec5639817c2
CAALookup not available with standard resolver
Resolved in 1047 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+
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

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

Preferred variant: non-www

HTTP → HTTPS

301http://tue.nl/ → https://tue.nl:443/

Consistent

A+
Domain Intelligence
tue.nl — via Technische Universiteit Eindhoven, 39 years, 4 months old, hosted on AS-TUE Technische Universiteit Eindhoven TUe, NL
PASS
tue.nl — via Technische Universiteit Eindhoven, 39 years, 4 months old, hosted on AS-TUE Technische Universiteit Eindhoven TUe, NL
Info::
DNSSEC is enabled
Info::
Registrar: Technische Universiteit Eindhoven
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: AS-TUE Technische Universiteit Eindhoven TUe, NL
Got: AS1161
Domain expiry

Unknown

SSL certificate

57 days

Issued by Let's Encrypt

Domain age

39 years, 4 months

Registered July 2, 1987

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

AS-TUE Technische Universiteit Eindhoven TUe, NL

ASN AS1161

131.155.10.135

Registrar

Technische Universiteit Eindhoven

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 Technische Universiteit Eindhoven
Created July 2, 1987 (39 years, 4 months ago)
Last Updated March 11, 2026
Name Servers ns01.tue.nl, ns02.tue.nl
DNSSEC Enabled
Registrant Technische Universiteit Eindhoven
Hosting
IP Address 131.155.10.135
ASN AS1161 (AS-TUE Technische Universiteit Eindhoven TUe, NL)
Provider AS-TUE Technische Universiteit Eindhoven TUe, NL
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

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

Send Feedback