Skip to content
https://unicef.org

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
6
PASS
11
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
17
11 PASS 6 REVIEW
B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 54.83.48.147 does not match any cert SAN: ec2-54-83-48-147.compute-1.amazonaws.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
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
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.unicef.org/
200https://unicef.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://unicef.org/ https://www.unicef.org/

Consistent

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

Certificate validity

169
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
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
A+
DNS Records
1 A records, 7 ms lookup
PASS
1 A records, 7 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 54.83.48.147
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns1-06.azure-dns.com, ns2-06.azure-dns.net, ns3-06.azure-dns.org, ns4-06.azure-dns.info
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 7 ms
Got: 7 ms
A54.83.48.147
AAAA
CNAME
NSns1-06.azure-dns.com, ns2-06.azure-dns.net, ns3-06.azure-dns.org, ns4-06.azure-dns.info
MX
0 unicef-org.mail.protection.outlook.com
TXT
013010
MS=ms48737485
MS=ms67199091
v=verifydomain MS=ms18350245
6X10w9vCHQbmK5Slfyb2fgoEXlAh5h70sbR2UNnhUHF0xNWfNpIKcQ09k0sDo39k0DAW6GkCgqjGbZma...
SPF v=spf1 include:spf.protection.outlook.com ip4:8.2.125.68 ip4:8.2.127.68 ip4:8.2....
docusign=47f819c4-6534-4a99-a238-7d907da02fd0
docusign=87cfe5cd-c6fd-4953-bc36-4671e8d876d6
mgverify=1d1106206db00656dd4492acd3c13bacc3ba6b4b6ddb421c825902be3bd2060b
google-site-verification=ilp04w8Yb-Dla4zi0gkrL8T4Y_pxXWBQ-4PlQAaZvAQ
teamviewer-sso-verification=9ba2d40719f74fbe9ddc96cba3058194
pexip-ms-tenant-domain-verification=1f03243e-6e7b-4ed3-ba00-84ab5e2e4bb8
_secpe34333aoiiquctabo0nfvsucx15
cursor-domain-verification-2s15mb=iGRRFCGY0QojHnnf9UxZ0tGpp
_c5t0cizd75jwwdtt039aqtanap9iycu
anthropic-domain-verification-7y3jg2=5ieq09lKvbr7KrSZv125WSVBQ
CAALookup not available with standard resolver
Resolved in 7 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

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A
CAA Records
issue: digicert.com | issuewild: digicert.com
PASS
issue: digicert.com | issuewild: digicert.com
Info::
CAA issue tag present — authorized CA(s): digicert.com
Info::
No CAA iodef tag — won't be notified of failed issuance attempts
Add `0 iodef "mailto:security@example.com"` to receive notifications when a CA refuses issuance because it doesn't match your CAA policy. Useful signal for detecting issuance attempts by unauthorized CAs.
A+
Multi-Resolver DNS Speed
Mean 5ms across 3 resolvers (spread 9ms)
PASS
Mean 5ms across 3 resolvers (spread 9ms)
Info::
Quad9: 2ms
Got: 2ms via 9.9.9.9:53
Info::
Cloudflare: 4ms
Got: 4ms via 1.1.1.1:53
Info::
Google: 11ms
Got: 11ms via 8.8.8.8:53
A
Redirect Chain
1 redirect(s), 338 ms total
PASS
1 redirect(s), 338 ms total
Info::
Single redirect
Got: https://unicef.org → https://www.unicef.org/ (301)
Info::
WWW normalization redirect

https://unicef.org

290 ms · HTTP/1.1

301

https://www.unicef.org/

48 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://unicef.org301290 msHTTP/1.1nginx
2https://www.unicef.org/20048 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 158 URLs
PASS
robots.txt present, sitemap with 158 URLs
Info::
robots.txt is present
Got: 1945 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 158 entries
Info::
Sitemap index with 158 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 1945 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

# 

# v0.1 - 2025-12-02


User-agent: *

# CSS, JS, Images

Allow: /core/*.css$

Allow: /core/*.css?

Allow: /core/*.js$

Allow: /core/*.js?

Allow: /core/*.gif

Allow: /core/*.jpg

Allow: /core/*.jpeg

Allow: /core/*.png

Allow: /core/*.svg

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: /profiles/*.svg

# Directories

Disallow: /core/

Disallow: /profiles/

# Files

Disallow: /README.txt

Disallow: /web.config

# Paths (clean URLs)

Disallow: /admin/

Disallow: /comment/reply/

Disallow: /filter/tips

Disallow: /node/

Disallow: /search/

Disallow: /search/*

Disallow: /*/search/

Disallow: /*/search/*

Disallow: /topics/

Disallow: /topics/*

Disallow: /*/topics/

Disallow: /*/topics/*

Disallow: /*/view-all/*

Disallow: /view-all/*

Disallow: /api/*

Disallow: /*/api/*

Disallow: /user/register/

Disallow: /user/password/

Disallow: /user/login/

Disallow: /user/logout/

# Paths (no clean URLs)

Disallow: /index.php/admin/

Disallow: /index.php/comment/reply/

Disallow: /index.php/filter/tips

Disallow: /index.php/node/

Disallow: /index.php/search/

Disallow: /index.php/user/password/

Disallow: /index.php/user/register/

Disallow: /index.php/user/login/

Disallow: /index.php/user/logout/

Disallow: /*unicef-component-mosaic
sitemap.xml 200 OK
Type Sitemap Index URLs 158 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
unicef.org — via CSC Corporate Domains, Inc., 33 years, 9 months old, hosted on AWS
PASS
unicef.org — via CSC Corporate Domains, Inc., 33 years, 9 months old, hosted on AWS
Info::
Domain registered until Mar 11, 2030 (3 years, 8 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: CSC Corporate Domains, Inc.
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: AS14618
Domain expiry

1336 days

March 11, 2030

SSL certificate

169 days

Issued by DigiCert Inc

Domain age

33 years, 9 months

Registered March 10, 1993

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

54.83.48.147

Registrar

CSC Corporate Domains, Inc.

Unlocked 4 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 CSC Corporate Domains, Inc.
Created March 10, 1993 (33 years, 9 months ago)
Expires March 11, 2030 (3 years, 8 months)
Last Updated February 21, 2021
Name Servers ns3-06.azure-dns.org, ns1-06.azure-dns.com, ns2-06.azure-dns.net, ns4-06.azure-dns.info
DNSSEC Not enabled
Hosting
IP Address 54.83.48.147
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

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

Connection waterfall

DNS Lookup 5 ms TCP Connect 95 ms TLS Handshake 102 ms Server Processing 96 ms Content Transfer 0 ms
A+
CDN & Delivery
Varnish (HIT)
PASS
Varnish (HIT)
Info::
Site is served via Varnish CDN
Got: via: varnish
Info::
CDN cache status: HIT
CDN Detected: Varnish
Provider Varnish Cache Status HIT Evidence via: varnish
A+
CDN Cache Observability
Cache state: HIT
PASS
Cache state: HIT
Info::
CDN cache state observable via 3 header(s)
Got: age=430069, x-cache=HIT, x-cache-hits=41411
A+
Health Check Endpoint
Health endpoint at https://unicef.org/health (HTTP 200)
PASS
Health endpoint at https://unicef.org/health (HTTP 200)
Info::
Public health endpoint at https://unicef.org/health
Got: https://unicef.org/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback