Skip to content
https://vrt.be

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
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
F
Redirect Chain
Action
3 redirect(s), 1078 ms total
FIX
3 redirect(s), 1078 ms total
Warning::
3 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1078 ms total
Got: 1078 ms

https://vrt.be

680 ms · HTTP/1.1

301

https://www.vrt.be/

172 ms · HTTP/1.1

301

https://www.vrt.be/nl/

185 ms · HTTP/1.1

308

https://www.vrt.be/nl

41 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://vrt.be301680 msHTTP/1.1awselb/2.0
2https://www.vrt.be/301172 msHTTP/1.1
3https://www.vrt.be/nl/308185 msHTTP/1.1Apache
4https://www.vrt.be/nl20041 msHTTP/1.1Apache

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

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

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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
2 A records, 841 ms lookup
PASS
2 A records, 841 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 76.223.91.55, 13.248.195.120
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: ns3.belnet.be, ns2.belnet.be, ns01.vrt.be, ns1.belnet.be, ns02.vrt.be
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 (841 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 841 ms
A76.223.91.55, 13.248.195.120
AAAA
CNAME
NSns3.belnet.be, ns2.belnet.be, ns01.vrt.be, ns1.belnet.be, ns02.vrt.be
MX
10 vrt-be.mail.protection.outlook.com
TXT
asv=872ec02e72db8d0304e5da9fab69750e
apple-domain-verification=DjerGRsmCWbOMqrr
jamf-site-verification=RLnGzFPmPZQb2ZDuVdD5vg
bw=6Qr/HeOrHherTgaUcETV4dnSNcJcIzQbwaRyGxApDwPT
miro-verification=9e435aa899b50cd6fab6532c2b9e336c2d84b35f
facebook-domain-verification=494j9w9ys53gyvf9zmt2ezwzaeqmfm
facebook-domain-verification=5zp0w0q800f3g7em9sx1zcy6f1alf7
facebook-domain-verification=gvu8tyslelle118rlji0fcnvckhlta
adobe-idp-site-verification=da03bd05-e3a1-407a-aca6-5ac87ad47611
google-site-verification=8OyAZtBl3kNVFutLIyPCleCTykhHIWuVDDwqYmzwvio
google-site-verification=CRevCXbCQZnr7dMQhWH693fwaCJust_JTh59xW9OVPw
google-site-verification=hrSWRgxUJfHqE80bUIjfT5wz2D3dWPH8zlxnk8QMgXA
google-site-verification=pOV0alfgtw5sxzcAkRwISyqgcv5MeEvvnvAylny3BFk
google-site-verification=uuTGE6XU1FZqVyY13S_-x1Vi2_6qqmsANKeZDG8PEgs
_globalsign-domain-verification=AGYGEZu0H-bSXOLZ25fpvhgeZ39BV8_93zhWwKvTVM
_globalsign-domain-verification=xCFa4Zqi0LVYkdUoPx1N_BRPDrfKkAQs34UdXSUbGg
atlassian-sending-domain-verification=f980cc66-fed3-4d4e-8e22-67a59d5b2672
SDbT71IMpKJqO+SpLWvKCTakkZteCvjO16+ORckO8a0FPzD+rW1epWA9QYZABKw/F9RqOIns9/M7GzLO...
atlassian-domain-verification=ZmnaMFH8Rogmh0egTpUUKEdl66D8oSL5nYBVTLkdUn9L/JkSvk...
atlassian-domain-verification=zYEr9Nnm5PXcwyO/OPWHGJezvaHknAlmcXJNd5kuqJH2h/m/ez...
SPF v=spf1 ip4:84.241.182.106 ip4:95.130.40.188 ip4:95.130.43.99 ip4:50.31.47.220 ip...
00d0y000000qtnpua2
rm_verify=3e14f5b3e7
HARICA-1qsxDd9Bkec2PK4XTig
HARICA-rrQJF8TWlfrddw0EZat
CAALookup not available with standard resolver
Resolved in 841 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.

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 255 URLs
PASS
robots.txt present, sitemap with 255 URLs
Info::
robots.txt is present
Got: 969 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 255 entries
Info::
Sitemap index with 255 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 969 B Sitemaps referenced 5 User-agents Claude-Web, Google-Extended, Meta-ExternalFetcher, PerplexityBot, cohere-ai, DuckAssistBot, *, AI2Bot, Diffbot, Amazonbot, Applebot-Extended, CCBot, FacebookBot, GPTBot, Meta-ExternalAgent, OAI-SearchBot, PerplexityUser, anthropic-ai, Bytespider, ChatGPT-User, ClaudeBot Blocking No — crawling allowed
User-agent: *
Disallow: /libs/
Disallow: /vrtnws/*?ref=
Disallow: /vrtnws/*linkId=
Disallow: /vrtnws/*/sso/callback*error
Disallow: /vrtnws/*teaser.marge
Disallow: /vrtnws/*?t=

User-agent: AI2Bot
User-agent: Amazonbot
User-agent: Applebot-Extended
User-agent: anthropic-ai
User-agent: Bytespider
User-agent: CCBot
User-agent: ChatGPT-User
User-agent: ClaudeBot
User-agent: Claude-Web
User-agent: cohere-ai
User-agent: Diffbot
User-agent: DuckAssistBot
User-agent: FacebookBot
User-agent: Google-Extended
User-agent: GPTBot
User-agent: Meta-ExternalAgent
User-agent: Meta-ExternalFetcher
User-agent: OAI-SearchBot
User-Agent: PerplexityBot
User-agent: PerplexityUser
Disallow: /vrtnws/

Sitemap: https://www.vrt.be/vrtnws/nl.sitemap-index.xml

Sitemap: https://www.vrt.be/vrtnws/en.sitemap-index.xml

Sitemap: https://www.vrt.be/vrtnws/fr.sitemap-index.xml

Sitemap: https://www.vrt.be/vrtnws/de.sitemap-index.xml

Sitemap: https://www.vrt.be/vrtnws/nl.news-sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 255 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

301https://www.vrt.be/
200https://vrt.be/

Preferred variant: non-www

HTTP → HTTPS

301http://vrt.be/ https://www.vrt.be/

Consistent

A+
Domain Intelligence
vrt.be — hosted on AWS
PASS
vrt.be — hosted on AWS
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: AWS
Got: AS16509
Domain expiry

Unknown

SSL certificate

244 days

Issued by Amazon

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

13.248.195.120

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 ns02.vrt.be, ns2.belnet.be, ns3.belnet.be, ns01.vrt.be, ns1.belnet.be
Registrant Not shown, please visit www.dnsbelgium.be for webbased whois.
Hosting
IP Address 13.248.195.120
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
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 682 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
149 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
2 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
385 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
682 ms
Total Time Total request time from DNS lookup through full response.
682 ms

Connection waterfall

DNS Lookup 149 ms TCP Connect 2 ms TLS Handshake 385 ms Server Processing 146 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