Infrastructure - https://itu.int BeaverCheck Audit

F

Redirect Chain

Action

4 redirect(s), 4637 ms total

FIX

4 redirect(s), 4637 ms total

4 redirects before reaching final URL

Each redirect adds latency. Try to minimize the chain to 1 hop.

WWW normalization redirect

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://www.itu.int/

Redirect overhead: 4637 ms total

Got: 4637 ms

https://itu.int

727 ms · HTTP/1.1

301

https://www.itu.int/

802 ms · HTTP/1.1

302

https://www.itu.int/Pages/VariationRoot....

904 ms · HTTP/1.1

302

https://www.itu.int/en

787 ms · HTTP/1.1

302

https://www.itu.int/en/Pages/default.asp...

1417 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol
1	https://itu.int	301	727 ms	HTTP/1.1
2	https://www.itu.int/	302	802 ms	HTTP/1.1
3	https://www.itu.int/Pages/VariationRoot....	302	904 ms	HTTP/1.1
4	https://www.itu.int/en	302	787 ms	HTTP/1.1
5	https://www.itu.int/en/Pages/default.asp...	200	1417 ms	HTTP/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

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

Crawlability

robots.txt present, no sitemap

REVIEW

robots.txt present, no sitemap

robots.txt is present

Got: 1574 bytes

No sitemap.xml found

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

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 1574 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed

User-agent: *
Disallow: /itudocs/
Disallow: /itudocr/
Disallow: /res/
Disallow: /cres/
Disallow: /lib/
Disallow: /cgi-bin/
Disallow: /itu_mt_main 
Disallow: /testweb
Disallow: /dms_pub/itu-d/md/02/isap2b.1.1/c/D02-ISAP2B.1.1-C-0002*
Disallow: /dms_pub/itu-d/md/02/isap2b.1.1.1/c/D02-ISAP2B.1.1.1-C-0003*
Disallow: /dms_pub/itu-s/md/13/wtpf13/adm/S13-WTPF13-ADM-0010*
Disallow: /dms_pub/itu-t/md/05/universities/c/T05-UNIVERSITIES-C-0039*
Disallow: /dms_pub/itu-t/md/05/fg.fitcar/adm/T05-FG.FITCAR-ADM-0002*
Disallow: /dms_pub/itu-s/md/03/wsispc3/adm/S03-WSISPC3-ADM-0005*
Disallow: /dms_pub/itu-t/md/13/fg.carcom/adm/T13-FG.CARCOM-ADM-0025*
Disallow: /dms_pub/itu-t/oth/26/04/T260400000E*
Disallow: /dms_pub/itu-t/oth/26/06/T2606000004*
Disallow: /dms_pub/itu-t/oth/06/34/T0634000009*
Disallow: /dms_pub/itu-t/oth/06/39/T0639000008*
Disallow: /dms_pub/itu-t/oth/06/1D/T061D000011*
Disallow: /dms_pub/itu-r/oth/0C/08/R0C08000003*
Disallow: /dms_pub/itu-r/oth/0B/01/R0B01000005*
Disallow: /dms_pub/itu-t/oth/3D/04/T3D04000002*
Disallow: /dms_pub/itu-r/oth/0C/07/R0C07000050*
Disallow: /dms_pub/itu-t/oth/3D/01/T3D01000003*
Disallow: /dms_pub/itu-t/oth/3D/05/T3D05000003*
Disallow: /dms_pub/itu-t/oth/26/02/T2602000010*
Disallow: /dms_pub/itu-t/oth/06/42/T0642000005*
Disallow: /dms_pub/itu-t/oth/06/06/T060600000A*
Disallow: /dms_pub/itu-t/oth/06/0F/T060F000011*
Disallow: /dms_pub/itu-t/oth/06/49/T0649000002*
Disallow: /dms_pub/itu-t/oth/06/28/T0628000008*
Disallow: /dms_pub/itu-r/oth/0A/0E/R0A0E00008B*
Disallow: /dms_pub/itu-t/oth/06/15/T061500000C*
Disallow: /dms_priv/*

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B

HTTP Probe Timing

Total 961 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

232 ms

TCP Connect

242 ms

TLS Handshake

247 ms

Time to First Byte

961 ms

Total Time

961 ms

Connection waterfall

DNS Lookup 232 ms TCP Connect 242 ms TLS Handshake 247 ms Server Processing 240 ms Content Transfer 0 ms

B

TLS Certificate Expiry & Recommendations

61 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

61

days left

0d 30d 60d 90d+

Recommended actions

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

1 A records, 254 ms lookup

PASS

1 A records, 254 ms lookup

Resolves to 1 IPv4 address(es)

Got: 156.106.253.250

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

Has 1 IPv6 (AAAA) record(s)

Got: 2a00:7580:60:a252::3250

7 nameserver(s) configured

Got: ns.itu.ch, ns2.itu.ch, ns3.itu.ch, ns5.itu.ch, ns6.itu.ch, ns7.itu.ch, ns8.itu.ch

1 mail exchanger(s) configured

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

SPF record present in TXT

DNS resolution is slow (254 ms)

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

Got: 254 ms

A	156.106.253.250
AAAA	2a00:7580:60:a252::3250
CNAME	—
NS	ns.itu.ch, ns2.itu.ch, ns3.itu.ch, ns5.itu.ch, ns6.itu.ch, ns7.itu.ch, ns8.itu.ch
MX	28 itu-int.mail.protection.outlook.com
TXT	google-site-verification=OAL7V9LOPx_KZ3pTK2B89gxf9-tpX4SuWsujyfFxo5M UtNf3/9YCnOlqyKq55I859zREUJ3vIEafS4HVQpD/NcAts7kNSCo6e72jl7348oBAZqveiJc9cv7Fl25... google-site-verification=H4hEnSrSL9A-LU_zr1GB86qJ9TNwO5QQ62yVPDGxtQU cisco-ci-domain-verification=65b81f5e5cbb148bc6ecf3dbbe8a12c57a775321fb55e5b19be... atlassian-domain-verification=74JS2eOA8Lqcdxbs5ydH5jf1oZwmrm7egDaiC06Exhuraiecdu... apple-domain-verification=8k1jFouBaGXq2Vu4 SPF v=spf1 ip4:156.106.192.20/30 ip4:156.106.192.38/31 include:spf.protection.outloo... MS=ms10801744 adobe-idp-site-verification=45cc586968520745b7c4a80da26402a4e93b36523cb57fe997f1... google-site-verification=Mt2O1S2bdYkwzokESyNQlj-W_krcAAnJpKXW8YQBPZM google-site-verification=KnjD3vfQw6QzV-Tdi1DYB-vruU1LRfcoZa3hpu_6Dmw
CAA	Lookup not available with standard resolver

Resolved in 254 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+

IPv6 Readiness

IPv6 reachable (197 ms)

PASS

IPv6 reachable (197 ms)

IPv6 is configured and reachable at 2a00:7580:60:a252::3250

Got: 197 ms connect

IPv6 Ready

AAAA Records 2a00:7580:60:a252::3250 Connection Reachable (197 ms)

A

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

www/non-www redirect configured correctly (preferred: non-www)

HTTP→HTTPS redirect uses 302 instead of 301

Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

302https://www.itu.int/

200https://itu.int/

Preferred variant: non-www

HTTP → HTTPS

302http://itu.int/ → https://itu.int/

Use 301 (permanent) instead of 302 (temporary)

A+

Domain Intelligence

itu.int — 30 years, 2 months old

PASS

itu.int — 30 years, 2 months old

DNSSEC is not enabled

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

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.

Domain expiry

Unknown

SSL certificate

61 days

Issued by Let's Encrypt

Domain age

30 years, 2 months

Registered July 8, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a00:7580:60:a252::3250

Registrar

Registrar unknown

Unlocked 7 NS records

Expiry timeline

Today

+1 year

SSL expiry Danger zone (≤30 days)

Recommended actions

Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar

Created July 8, 1996 (30 years, 2 months ago)

Last Updated November 8, 2023

Name Servers ns.itu.ch, ns2.itu.ch, ns3.itu.ch, ns5.itu.ch, ns6.itu.ch, ns7.itu.ch, ns8.itu.ch

DNSSEC Not enabled

Registrant International Telecommunication Union

Hosting

IP Address 2a00:7580:60:a252::3250

Data source: rdap (0.8s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

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