Skip to content
https://unodc.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
75
GRADE
C
FIX
2
REVIEW
3
PASS
3
INFO
1
Probed from Amsterdam, Netherlands
302 Found
Checks
9
3 PASS 3 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 302 Expected: 301 redirect to HTTPS

www / non-www

200https://www.unodc.org/
200https://unodc.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://unodc.org/ → //www.unodc.org/

HTTP version does not redirect to HTTPS

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, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 268 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 268 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /enl/
Disallow: /site-search*.html
Disallow: /unodc/site-search.html
Disallow: /unodc/en/site-search.html
Disallow: /unodc/search.html
Disallow: /unodc/en/search.html
Disallow:/frontdoor/
Disallow:/cgi-bin/
Disallow:/test/
Disallow:/multimedia/
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

266
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, 47 ms lookup
PASS
1 A records, 47 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 193.138.94.114
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.unvienna.org, ns02.unvienna.org
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
Info::
DNS resolution time: 47 ms
Got: 47 ms
A193.138.94.114
AAAA—
CNAME—
NSns01.unvienna.org, ns02.unvienna.org
MX
10 unodc-org.mail.protection.outlook.com
TXT
google-site-verification=OcpOLRHAnU39VlpOxAt-Geq4An8HgpDpxHnBdS1zV2M
MS=ms33019253
linkedin-site-verification=794b5796-96d3-4deb-8406-e7fb69a5eda9
SPF v=spf1 ip4:193.138.94.0/24 include:un.org ip4:157.150.240.47 ip4:157.150.241.47 ...
_globalsign-domain-verification=hzmOX79NC0GjWjlTTr6SVhC8stFuvAEyBHG2xY85d4
CAALookup not available with standard resolver
Resolved in 47 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), 400 ms total
PASS
1 redirect(s), 400 ms total
Info::
Single redirect
Got: https://unodc.org → https://www.unodc.org/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://unodc.org

https://unodc.org

139 ms · HTTP/1.1

302

https://www.unodc.org/

262 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://unodc.org302139 msHTTP/1.1
2https://www.unodc.org/200262 msHTTP/1.1Apache

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

Connection waterfall

DNS Lookup 21 ms TCP Connect 20 ms TLS Handshake 59 ms Server Processing 20 ms Content Transfer 0 ms
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

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

Send Feedback