Skip to content
https://www.imf.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from Singapore, Singapore
307 Temporary Redirect
Checks
9
4 PASS 3 REVIEW 2 FIX
F
Redirect Chain
Action
3 redirect(s), 1525 ms total
FIX
3 redirect(s), 1525 ms total
Warning::
3 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Warning::
Redirect overhead: 1525 ms total
Got: 1525 ms

https://www.imf.org

408 ms · HTTP/1.1

307

https://www.imf.org/en/

319 ms · HTTP/1.1

308

https://www.imf.org/en

401 ms · HTTP/1.1

307

https://www.imf.org/en/home

397 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.imf.org307408 msHTTP/1.1Vercel
2https://www.imf.org/en/308319 msHTTP/1.1Vercel
3https://www.imf.org/en307401 msHTTP/1.1Vercel
4https://www.imf.org/en/home200397 msHTTP/1.1Vercel

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

F
HTTP Probe Timing
Action
Total 5593 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
5.11 s
TCP Connect TCP Connect — time to establish a TCP connection to the server.
77 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
83 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
5.59 s
Total Time Total request time from DNS lookup through full response.
5.59 s

Connection waterfall

DNS Lookup 5.11 s TCP Connect 77 ms TLS Handshake 83 ms Server Processing 328 ms Content Transfer 0 ms
B
DNS Records
2 A records, 92 ms lookup
REVIEW
2 A records, 92 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 184.51.102.106, 184.51.102.131
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2600:1417:8400:1f::17c8:e530, 2600:1417:8400:1f::17c8:e532
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: www.imf.org.edgekey.net
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 92 ms
Got: 92 ms
A184.51.102.106, 184.51.102.131
AAAA2600:1417:8400:1f::17c8:e530, 2600:1417:8400:1f::17c8:e532
CNAMEwww.imf.org.edgekey.net
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 92 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

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

Certificate validity

81
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
B
CDN & Delivery
Vercel
REVIEW
Vercel
Info::
Site is served via Vercel CDN
Got: x-vercel-id: pdx1::cnxlz-1775323170561-1b1ccca14939
CDN Detected: Vercel
Provider Vercel Evidence x-vercel-id: pdx1::cnxlz-1775323170561-1b1ccca14939
A+
IPv6 Readiness
IPv6 reachable (34 ms)
PASS
IPv6 reachable (34 ms)
Info::
IPv6 is configured and reachable at 2600:1417:8400:1f::17c8:e530, 2600:1417:8400:1f::17c8:e532
Got: 34 ms connect
IPv6 Ready
AAAA Records 2600:1417:8400:1f::17c8:e530, 2600:1417:8400:1f::17c8:e532 Connection Reachable (34 ms)
A
Crawlability
robots.txt present, no sitemap
PASS
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 450 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt references 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

robots.txt 200 OK
Size 450 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /external/country/

Disallow: /external/np/a4pilot/1999/

Disallow: /external/np/a4pilot/2000/

Disallow: /external/np/res/mmod/

Disallow: /external/np/term/

Disallow: /external/np/tre/tad/

Disallow: /external/ns/

Disallow: /external/pa4158/

Disallow: /external/pubs/FT/GFSR/*index.htm/

Disallow: /external/pubs/ft/weo/*index.htm/

Disallow: /forum/

Disallow: /presentation/

Sitemap: https://www.imf.org/sitemap.xml


sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.imf.org/
302https://imf.org/

Preferred variant: www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
imf.org — via CSC Corporate Domains, Inc., 32 years, 11 months old, hosted on Akamai
PASS
imf.org — via CSC Corporate Domains, Inc., 32 years, 11 months old, hosted on Akamai
Info::
Domain registered until Oct 12, 2026 (6 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.
Info::
Hosting: Akamai
Got: AS20940
Domain expiry

118 days

October 12, 2026

SSL certificate

81 days

Issued by DigiCert Inc

Domain age

32 years, 11 months

Registered October 13, 1993

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Akamai

ASN AS20940

184.51.102.106

Registrar

CSC Corporate Domains, Inc.

Lock status unknown 6 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
Registrar CSC Corporate Domains, Inc.
Created October 13, 1993 (32 years, 11 months ago)
Expires October 12, 2026 (6 months)
Last Updated October 13, 2025
Name Servers a1-153.akam.net, a22-66.akam.net, a28-67.akam.net, a4-64.akam.net, a7-65.akam.net, a9-66.akam.net
DNSSEC Not enabled
Hosting
IP Address 184.51.102.106
ASN AS20940 (AKAMAI-ASN1, NL)
Provider Akamai
Data source: rdap (2.0s)

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

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

Send Feedback