Skip to content
https://ugent.be

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 4 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
Crawlability
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 882 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt references sitemap

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

robots.txt 200 OK
Size 882 B Sitemaps referenced 1 User-agents *, Googlebot Blocking No — crawling allowed
Sitemap: https://www.ugent.be/sitemap.xml.gz


# Define access-restrictions for robots/spiders

# http://www.robotstxt.org/wc/norobots.html




# By default we allow robots to access all areas of our site

# already accessible to anonymous users


User-agent: *

Disallow: /intranet




# Add Googlebot-specific syntax extension to exclude forms

# that are repeated for each piece of content in the site

# the wildcard is only supported by Googlebot

# http://www.google.com/support/webmasters/bin/answer.py?answer=40367&ctx=sibling


User-Agent: Googlebot

Disallow: /*?

Disallow: /*atct_album_view$

Disallow: /*folder_factories$

Disallow: /*folder_summary_view$

Disallow: /*login_form$

Disallow: /*mail_password_form$

Disallow: /@@search

Disallow: /*search_rss$

Disallow: /*sendto_form$

Disallow: /*summary_view$

Disallow: /*thumbnail_view$

Disallow: /*view$
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
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.ugent.be/
200https://ugent.be/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://ugent.be/ https://ugent.be/

Consistent

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

Certificate validity

187
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 DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 29 ms lookup
PASS
1 A records, 29 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 157.193.43.50
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: ns1.belnet.be, ns2.belnet.be, ns1.ugent.be, ns2.ugent.be, ns3.belnet.be
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: 29 ms
Got: 29 ms
A157.193.43.50
AAAA
CNAME
NSns1.belnet.be, ns2.belnet.be, ns1.ugent.be, ns2.ugent.be, ns3.belnet.be
MX
20 smtpfltrp2.ugent.be
20 smtpfltrp1.ugent.be
TXT
spycloud-domain-verification=9a7c586f-0713-499b-9346-3ea48e997b95
atlassian-domain-verification=fr/DNQv3XF8SaHu8Eax8RbokaSc/G/YZzxEXx8mDEIQael0c8N...
HtoaiDPViPUv0A4dm6+s28moKLPa7BPtJbwm21gun1Pam0QWoysVybqy0yxPyeXTZNmZ34Xj6VZqGhzm...
google-site-verification=FJbCHY-GpXqJs0BjL-NSgWP-BiSZvVrdg7LFCqVTSFo
X5mSkxz0=38f94eb1ae25089899dbc0272d2f1ca9
successfactors-site-verification=NzA3YjdkMzY2YTU2ZGI2YTllOTVkOWRiMDRjZmY2ZGZiNWU...
facebook-domain-verification=j8csxhbt4b7g011xkkyp2ntj8c4agx
MS=2894DC27171D559D51E2C8E2EE4343C9639943B4
SPF v=spf1 include:_spf.ugent.be -all
google-site-verification=h631AHN5FSFPqRWajHSO6fNPlvCh18LAz77-XPt3H2o
HARICA-jhPvVhwGq6lWpe4EQdY
CAALookup not available with standard resolver
Resolved in 29 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.

A
Redirect Chain
1 redirect(s), 226 ms total
PASS
1 redirect(s), 226 ms total
Info::
Single redirect
Got: https://ugent.be → https://www.ugent.be/ (301)
Info::
WWW normalization redirect

https://ugent.be

99 ms · HTTP/1.1

301

https://www.ugent.be/

127 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ugent.be30199 msHTTP/1.1Apache
2https://www.ugent.be/200127 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
ugent.be — hosted on BELNET, BE
PASS
ugent.be — hosted on BELNET, BE
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: BELNET, BE
Got: AS2611
Domain expiry

Unknown

SSL certificate

187 days

Issued by Hellenic Academic and Research Institutions CA

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

BELNET, BE

ASN AS2611

157.193.43.50

Registrar

Registrar unknown

Unlocked 5 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
Name Servers ns3.belnet.be, ns1.ugent.be, ns2.ugent.be, ns1.belnet.be, ns2.belnet.be
Registrant Not shown, please visit www.dnsbelgium.be for webbased whois.
Hosting
IP Address 157.193.43.50
ASN AS2611 (BELNET, BE)
Provider BELNET, BE
Data source: whois (0.7s)

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 126 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
26 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
30 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.
127 ms
Total Time Total request time from DNS lookup through full response.
127 ms

Connection waterfall

DNS Lookup 26 ms TCP Connect 30 ms TLS Handshake 37 ms Server Processing 33 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