Skip to content
https://un.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
302 Found
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, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 2226 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 2226 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used:    http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html

User-agent: *
Crawl-delay: 10
# CSS, JS, Images
Allow: /misc/*.css$
Allow: /misc/*.css?
Allow: /misc/*.js$
Allow: /misc/*.js?
Allow: /misc/*.gif
Allow: /misc/*.jpg
Allow: /misc/*.jpeg
Allow: /misc/*.png
Allow: /modules/*.css$
Allow: /modules/*.css?
Allow: /modules/*.js$
Allow: /modules/*.js?
Allow: /modules/*.gif
Allow: /modules/*.jpg
Allow: /modules/*.jpeg
Allow: /modules/*.png
Allow: /profiles/*.css$
Allow: /profiles/*.css?
Allow: /profiles/*.js$
Allow: /profiles/*.js?
Allow: /profiles/*.gif
Allow: /profiles/*.jpg
Allow: /profiles/*.jpeg
Allow: /profiles/*.png
Allow: /themes/*.css$
Allow: /themes/*.css?
Allow: /themes/*.js$
Allow: /themes/*.js?
Allow: /themes/*.gif
Allow: /themes/*.jpg
Allow: /themes/*.jpeg
Allow: /themes/*.png
# Directories
Disallow: /includes/
Disallow: /misc/
Disallow: /modules/
Disallow: /profiles/
Disallow: /scripts/
Disallow: /themes/
Disallow: /en/internaljustice/files/
# Files
Disallow: /CHANGELOG.txt
Disallow: /cron.php
Disallow: /INSTALL.mysql.txt
Disallow: /INSTALL.pgsql.txt
Disallow: /INSTALL.sqlite.txt
Disallow: /install.php
Disallow: /INSTALL.txt
Disallow: /LICENSE.txt
Disallow: /MAINTAINERS.txt
Disallow: /update.php
Disallow: /UPGRADE.txt
Disallow: /xmlrpc.php
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips/
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register/
Disallow: /user/password/
Disallow: /user/login/
Disallow: /user/logout/
# Paths (no clean URLs)
Disallow: /?q=admin/
Disallow: /?q=comment/reply/
Disallow: /?q=filter/tips/
Disallow: /?q=node/add/
Disallow: /?q=search/
Disallow: /?q=user/password/
Disallow: /?q=user/register/
Disallow: /?q=user/login/
Disallow: /?q=user/logout/

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

C
URL Variants
Action
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.un.org/
200https://un.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://un.org/ https://un.org/

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

142
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
  • 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
2 A records, 261 ms lookup
PASS
2 A records, 261 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 157.150.185.49, 157.150.185.92
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns3.un.org, ns1.un.org, ns2.un.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
Warning::
DNS resolution is slow (261 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 261 ms
A157.150.185.49, 157.150.185.92
AAAA
CNAME
NSns3.un.org, ns1.un.org, ns2.un.org
MX
0 un-org.mail.protection.outlook.com
TXT
SPF v=spf1 include:_netblocks.un.org include:_netblocks2.un.org include:_spf.google....
teamviewer-sso-verification=fde5c90fdb764da199caa79160aef58b
atlassian-sending-domain-verification=1d232bde-ddc5-4e81-84a4-5fc29c17acdf
atlassian-sending-domain-verification=685ec4a1-3cfc-4ffa-8d51-9f6bb6f07baa
cisco-ci-domain-verification=71023db9cebccd164d6c6916b649179c4109a8bf4a53206db80...
FOhfWhsJtJ/FZcqQdLjqBNwOqynP/KX4ozWsJFw+k50mDbWjv05zbvEonHMzMIKP9XSZ77kWWuilSHT/...
brevo-code:4258a8aaff2c4cc4d4f46631ee3f416d
iContact1651565
atlassian-domain-verification=FTWfMaOalWt6nDxqxSGymL9Ey/KoIooB7a1zLsjL5bvuQbXb/C...
amazonses:cq717whOBbl30dhYr9HtG5aBpZfmtVwZ8/8TyeUrXh8=
xrqyoOBvFUFgFNdafNF3eo+zN4SEGAc+1gcHkfcbobjGa/UFAkMc/rCWUxywPjgWU1yMIYtuFAnHfLXd...
mandrill_verify.J6D4EK4DxGiLqR1nMTfHSA
j9lgbXbR0aOn/a3/tHAIQ1aK4uhUriBVu4/6I88jmBK0NyrCV36RIyrHwXouU3F0uQSEK0EPj6eBZ/Tc...
brevo-code:0502b29d26710cfe3a7f5a6713f7b141
adobe-idp-site-verification=44b9613bd417076c4622079494211a8fb11053a66a37a841db2e...
cisco-ci-domain-verification=3be0a328c387dcfe19bfab64b24e33f04b04e2065771adbc404...
google-site-verification=dFG8i5QSNlXCckN62lWWTmmj7TEVkVh_G82rHzMPeaE
sendinblue-code:c80931e2ffea8fadc62c1bfb5141f449
MS=ms26002463
apple-domain-verification=yaMAnI0GjK2mwjBL
00D2E000000pRe2=1TBVK00000000o1
atlassian-domain-verification=4qBZ2F7TUigBgD7l6Ate/ExncM2HVQU855IzHmcHurVkPVGUU6...
brevo-code:8016bd7e8b58b2c44d2253f7a674b1f9
d365mktkey=GU4x93TE2dUlhH2NSdB6v7gbxcKnvDje0eF8WD0rNnUx
atlassian-sending-domain-verification=030cf619-e1ff-4c61-b2ff-0b8bf31422e8
atlassian-sending-domain-verification=b818d67b-c504-4b82-a2ac-fb1ffa5dd99e
_globalsign-domain-verification=InsBxD8bdOtSqNib2b8QE1vAWRL07fy1C1VP9BHZO1
56a37f487f3361c43f8c285de2f7f60839ac3a7f1bd37b37353ecd343c995fa2
fastly-domain-delegation-xss3y9gtai43byf7o4ey-00458132-2025-07-09
webexdomainverification.4C675B882DC2B136E053AB06FC0A3F65=6652b0a5-c301-4a9f-8629...
rij4mb6stfqk9nqp6db054r4se
atlassian-domain-verification=1rY0mwP3xqUqI0Z6SVEdrrPHJ4hquQL28GrmRTVZ6/IZMKDmPs...
CAALookup not available with standard resolver
Resolved in 261 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
Redirect Chain
1 redirect(s), 625 ms total
PASS
1 redirect(s), 625 ms total
Info::
Single redirect
Got: https://un.org → https://www.un.org/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://un.org
Info::
Redirect overhead: 625 ms total
Got: 625 ms

https://un.org

431 ms · HTTP/1.1

302

https://www.un.org/

194 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://un.org302431 msHTTP/1.1
2https://www.un.org/200194 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+
Domain Intelligence
un.org — via Network Solutions, LLC, 31 years, 7 months old, hosted on ORANGE-BUSINESS-NAM, IE
PASS
un.org — via Network Solutions, LLC, 31 years, 7 months old, hosted on ORANGE-BUSINESS-NAM, IE
Info::
Domain registered until Feb 1, 2029 (2 years, 10 months remaining)
Info::
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.
Info::
Registrar: Network Solutions, LLC
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: ORANGE-BUSINESS-NAM, IE
Got: AS2647
Domain expiry

899 days

February 1, 2029

SSL certificate

142 days

Issued by COMODO CA Limited

Domain age

31 years, 7 months

Registered January 31, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

ORANGE-BUSINESS-NAM, IE

ASN AS2647

157.150.185.49

Registrar

Network Solutions, LLC

Unlocked 3 NS records
Expiry timeline
Today
+1 year
Domain expiry 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 Network Solutions, LLC
Created January 31, 1995 (31 years, 7 months ago)
Expires February 1, 2029 (2 years, 10 months)
Last Updated September 3, 2025
Name Servers ns1.un.org, ns2.un.org, ns3.un.org
DNSSEC Not enabled
Hosting
IP Address 157.150.185.49
ASN AS2647 (ORANGE-BUSINESS-NAM, IE)
Provider ORANGE-BUSINESS-NAM, IE
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

A
HTTP Probe Timing
Total 451 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.
108 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
216 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
451 ms
Total Time Total request time from DNS lookup through full response.
451 ms

Connection waterfall

DNS Lookup 21 ms TCP Connect 108 ms TLS Handshake 216 ms Server Processing 107 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