Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.CCrawlabilityActionrobots.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
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
##############################
#
# ICC WebAdmins robots.txt
#
##############################
User-agent: *
Disallow: *
User-agent: Googlebot
Allow: *
# User-agent: *
# Disallow: /pki/
# Disallow: /english/tratop_e/sps_e/4th_sps_course_e/
# Disallow: /english/tratop_e/tbt_e/1st_tbt_course_e/
# Disallow: /english/thewto_e/minist_e/mc10_e/coordinator_guide_e.pdf
# Disallow: /english/thewto_e/minist_e/mc10_e/participant_guide_e.pdf
# Disallow: /french/thewto_f/minist_f/mc10_f/coordinator_guide_f.pdf
# Disallow: /french/thewto_f/minist_f/mc10_f/participant_guide_f.pdf
# Disallow: /spanish/thewto_s/minist_s/mc10_s/coordinator_guide_s.pdf
# Disallow: /spanish/thewto_s/minist_s/mc10_s/participant_guide_s.pdf
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BHTTP Probe TimingTotal 884 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations62 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
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 Records2 A records, 7 ms lookupPASS
| A | 104.18.41.190, 172.64.146.66 |
| AAAA | 2a06:98c1:3102::6812:29be, 2606:4700:4406::ac40:9242 |
| CNAME | — |
| NS | carmelo.ns.cloudflare.com, dawn.ns.cloudflare.com |
| MX | 0 wto-org.mail.protection.outlook.com |
| TXT | PP0tO1M adobe-idp-site-verification=40c271b7b29442eab58c97589992254436090b94e80f6ea97eae... SPF v=spf1 ip4:80.80.227.166 ip4:66.59.5.169 ip4:80.80.227.164 ip4:93.92.211.70 ip4:... vdf1qEx+I/Z+jtYM+ZyJQ/rkV7RwgRhqdCL24kUBXjt+XlRHA2X1GcyE3+H8YZIH30Uo+zU5XX++jShE... |
| 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.
ARedirect Chain1 redirect(s), 643 ms totalPASS
https://wto.org
238 ms · HTTP/1.1
https://www.wto.org/
405 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://wto.org | 302 | 238 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.wto.org/ | 200 | 405 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
If permanent, use 301 instead.
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+IPv6 ReadinessIPv6 reachable (2 ms)PASS
A+Domain Intelligencewto.org — via Network Solutions, LLC, 31 years, 5 months oldPASS
1771 days
April 20, 2031
62 days
Issued by Google Trust Services
31 years, 5 months
Registered April 19, 1995
Not enabled
Protects against DNS spoofing
Unknown
2a06:98c1:3102::6812:29be
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