Infrastructure - https://ifc.org BeaverCheck Audit

B

Redirect Chain

2 redirect(s), 309 ms total

REVIEW

2 redirect(s), 309 ms total

2 redirects before reaching final URL

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

WWW normalization redirect

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://ifc.org

https://ifc.org

66 ms · HTTP/1.1

302

https://www.ifc.org/

139 ms · HTTP/1.1

301

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

104 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://ifc.org	302	66 ms	HTTP/1.1	cloudflare
2	https://www.ifc.org/	301	139 ms	HTTP/1.1	cloudflare
3	https://www.ifc.org/en/home	200	104 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.

Why this matters

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

Source: Google Search Central / web.dev

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

C

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

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

TLS Certificate Expiry & Recommendations

179 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

179

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

CDN & Delivery

Cloudflare

REVIEW

Cloudflare

Site is served via Cloudflare CDN (edge: CDG)

Got: cf-ray: 9f0801a83a586f42-CDG

CDN Detected: Cloudflare

Provider Cloudflare Evidence cf-ray: 9f0801a83a586f42-CDG

A+

DNS Records

2 A records, 45 ms lookup

PASS

2 A records, 45 ms lookup

Resolves to 2 IPv4 address(es)

Got: 104.18.42.237, 172.64.145.19

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: ns-1768.awsdns-29.co.uk, ns-890.awsdns-47.net, ns-152.awsdns-19.com, ns-1281.awsdns-32.org

4 mail exchanger(s) configured

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

SPF record present in TXT

DNS resolution time: 45 ms

Got: 45 ms

A	104.18.42.237, 172.64.145.19
AAAA	—
CNAME	—
NS	ns-1768.awsdns-29.co.uk, ns-890.awsdns-47.net, ns-152.awsdns-19.com, ns-1281.awsdns-32.org
MX	10 wbvapiron01a.worldbank.org 10 wbvapiron02a.worldbank.org 10 wbvapiron03a.worldbank.org 10 wbvapiron04a.worldbank.org
TXT	apple-domain-verification=pwxmryTjbOxTlaH4 smartsheet-site-validation=h307jVZfaZ_sUVANcr_7pyhu_P3RlhZp SPF v=spf1 include:ifc.org._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.va... google-site-verification=uuUX1xCiXQ0lWr4ca9wIvBJSMPTiHkblp_BqO7HmyPs google-site-verification=JYVk18X7XCcVQ_Ekt8yz9JbJ8rP_BR9p7kDNjsUOuCk onetrust-domain-verification=0581f60e1dee4f5f8a537abb0d63e8de wrike-verification=NjM0ODAyOTo3ZDhmOThiNTc5ZDk0MDZlODg3NWM1OTdmMmQ4Y2VmMjI2ZmU2Y... remarkable-domain-verification=e858705e-f514-4e60-8c2b-3744a29d69b3 cisco-ci-domain-verification=5890464693d2d0e9fa98fed3c7dc60311f216146362cd542787... google-site-verification=ag1Rr17Ue2wmB6NCSvN67gnPy7AUBDGbRDv9rQvsvmM google-site-verification=2VWhRSjs4zsfUiXNSDHPBxWEpq0mBaNC9jLee5gkQJ4 insomnia-validation=c43a507aafe24875bfb5aff06993cac6446c4e7229695e2c9b3b17b355f6...
CAA	Lookup not available with standard resolver

Resolved in 45 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.

A+

Crawlability

robots.txt present, sitemap with 15 URLs

PASS

robots.txt present, sitemap with 15 URLs

robots.txt is present

Got: 231 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 15 entries

Sitemap index with 15 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 231 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed

User-agent: *
Allow:*
Disallow: */apps/*
Disallow: */libs/*
Disallow: */bin/*
Disallow: */wbg/services/*
Disallow: */misc*
Disallow: */conf/*
Disallow: */wbg/aem/*
Disallow: /en/disclosures/
Sitemap: https://www.ifc.org/sitemap.xml

sitemap.xml 200 OK

Type Sitemap Index URLs 15 entries Valid XML Yes

Child Sitemaps:

A

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

www/non-www redirect configured correctly (preferred: non-www)

HTTP→HTTPS redirect uses 302 instead of 301

Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

301https://www.ifc.org/

200https://ifc.org/

Preferred variant: non-www

HTTP → HTTPS

302http://ifc.org/ → https://www.ifc.org/

Use 301 (permanent) instead of 302 (temporary)

A+

Domain Intelligence

ifc.org — via Amazon Registrar, Inc., 30 years, 9 months old, hosted on Cloudflare

PASS

ifc.org — via Amazon Registrar, Inc., 30 years, 9 months old, hosted on Cloudflare

Domain registered until Dec 20, 2028 (2 years, 8 months remaining)

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.

Registrar: Amazon Registrar, Inc.

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.

Hosting: Cloudflare

Got: AS13335

Domain expiry

918 days

December 20, 2028

SSL certificate

179 days

Issued by CLOUDFLARE, INC.

Domain age

30 years, 9 months

Registered December 21, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

172.64.145.19

Registrar

Amazon Registrar, 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 Amazon Registrar, Inc.

Created December 21, 1995 (30 years, 9 months ago)

Expires December 20, 2028 (2 years, 8 months)

Last Updated February 3, 2023

Name Servers ns-1281.awsdns-32.org, ns-152.awsdns-19.com, ns-1768.awsdns-29.co.uk, ns-890.awsdns-47.net

DNSSEC Not enabled

Hosting

IP Address 172.64.145.19

ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)

Provider Cloudflare

Data source: rdap (0.5s)

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 119 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

50 ms

TCP Connect

16 ms

TLS Handshake

21 ms

Time to First Byte

119 ms

Total Time

119 ms

Connection waterfall

DNS Lookup 50 ms TCP Connect 16 ms TLS Handshake 21 ms Server Processing 31 ms Content Transfer 0 ms