Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BRedirect Chain2 redirect(s), 292 ms totalREVIEW
https://fao.org
75 ms · HTTP/1.1
http://www.fao.org/home/en
76 ms · HTTP/1.1
https://www.fao.org/home/en
141 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://fao.org | 301 | 75 ms | HTTP/1.1 | cloudflare |
| 2 | http://www.fao.org/home/en | 301 | 76 ms | HTTP/1.1 | cloudflare |
| 3 | https://www.fao.org/home/en | 200 | 141 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
Redirect directly from https://fao.org to https://www.fao.org/home/en
Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.
Source: web.dev
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BCrawlabilityrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.
Learn more ▾ ▴
Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.
Source: sitemaps.org / Google Search Central
An empty sitemap provides no value. Add <url> entries for your pages.
An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.
Learn more ▾ ▴
Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.
Source: Google Search Central / sitemaps.org
Sitemap: https://www.fao.org/newsroom/sitemap/sitemap.gz
Sitemap: https://www.fao.org/in-action/ectad/sitemap/sitemap.gz
Sitemap: https://www.fao.org/americas/sitemap/sitemap.gz
Sitemap: https://www.fao.org/director-general/sitemap/sitemap-index.xml
Sitemap: https://www.fao.org/europe/sitemap/sitemap.gz
Sitemap: https://www.fao.org/world-food-day/sitemap/sitemap.gz
User-agent: *
Disallow: /index.php
Disallow: /t3lib/ # Nothing to see here
Disallow: /typo3/ # Nothing to see here
#Google needs to read CSS and JS here - nw 29 Jul 2015 # Disallow: /typo3conf/
#Google needs to read CSS and JS here - nw 29 Jul 2015 # Disallow: /typo3temp/
Disallow: /*?id=* #Disable non-realurl - re-instated 10/Oct/2013
Disallow: /*&type=98 #- specified in Google webmaster tools for the Google exclusion - re-instated 10/Oct/2013
Disallow: /fileadmin/user_upload/PermRep/ #don't need to be indexed (23/06/2014 - nw)
Disallow: /fileadmin/user_upload/en/ #don't need to be indexed (11/07/2014 - permreps)
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Preferred variant: non-www
HTTP → HTTPS
HTTP version does not redirect to HTTPS
BTLS Certificate Expiry & Recommendations251 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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
BCDN & DeliveryCloudflareREVIEW
A+DNS Records2 A records, 72 ms lookupPASS
| A | 104.18.22.5, 104.18.23.5 |
| AAAA | — |
| CNAME | — |
| NS | ns-1022.awsdns-63.net, ns-120.awsdns-15.com, ns-1878.awsdns-42.co.uk, ns-1289.awsdns-33.org |
| MX | 10 mx2.hc673-36.c3s2.iphmx.com 10 mx1.hc673-36.c3s2.iphmx.com |
| TXT | tl8tjhd3zwlmc7d5p8v59fcnsls1xmcg google-site-verification=O-daTNvtPqmVLHaEoDkssUiJOKIQM1pwIgxWpN2x_7I SPF v=spf1 mx ip4:168.202.0.0/16 ip4:216.71.156.249 ip4:216.71.157.59 ip4:216.71.158... google-site-verification=8_hK3sk05aXpxsUMkxtgmXtUpz-PIyIXI-W465ZZZPM atlassian-domain-verification=k/d/rw13K+FcfiZIf35VcOLrOsJKiB7yRlOpLzNTovS+0XtS16... google-site-verification=FSFz4FoqF-4qNtiGnsOF_15bq6R8kIjZbdd6TkRTB0E google-site-verification=mBt8u6Ql-vC32OvsZsQlzuU3XtxR8jp86qF_tF166Zo MS=ms31674077 google-site-verification=EdaM1nXRyjO8EkNBYPtgIkBqLPaqWunTEhdJQmSS6C0 _ylidrl0sdt7vedk5av7xv6qhf9nirns vx2s583k3qc965mjn1wp4srr5x196mkw fao.org=ad3797dc5ed64bec8915e53d2a444a46 docusign=9b82d061-6ff5-48be-9d76-c95d6e955485 google-site-verification=2AlwZ2NFbdxWw4IrxBWuahgXxguh8H2f9C2cDMjHVaI google-site-verification=QlcZkbraBDuhyHnCnbbarpYM5lO0He6v8w9EsNlgT6Q google-site-verification=TGJWizDpyrmC3-sv-ZZ4b52zsQx3yCCKeMll8X6uRMc google-site-verification=Cmk3P6tNog8tjKjf2pOCNZA8LwtnrLxzeFzKRdoSFoI abuseipdb-verification=iUUf8T3c google-site-verification=8wgJQhLKpWATYK8cNnDtr3ftr6gSH9VhPk5wsTnH8pY m6b8t2hxmpttsw6rc3kxdpltjxygmz98 YD40koslg1CHPZalTWsp7toTxP/K2u21KT4QHmThlB/fIMfAsCUMY7aG+FyFGkN6qtn6iruMFX2W+O2+... |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
A+Domain Intelligencefao.org — via Network Solutions, LLC, 33 years, 2 months old, hosted on CloudflarePASS
2951 days
July 13, 2034
251 days
Issued by DigiCert Inc
33 years, 2 months
Registered July 14, 1993
Not enabled
Protects against DNS spoofing
Cloudflare
ASN AS13335
104.18.22.5
Network Solutions, LLC
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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