Infrastructure - https://iisd.org BeaverCheck Audit

D

CDN & Delivery

Action

No CDN detected

FIX

No CDN detected

A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.

No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B

Redirect Chain

1 redirect(s), 1875 ms total

REVIEW

1 redirect(s), 1875 ms total

Single redirect

Got: https://iisd.org → https://www.iisd.org:443/ (301)

WWW normalization redirect

Redirect overhead: 1875 ms total

Got: 1875 ms

https://iisd.org

840 ms · HTTP/1.1

301

https://www.iisd.org:443/

1035 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://iisd.org	301	840 ms	HTTP/1.1	awselb/2.0
2	https://www.iisd.org:443/	200	1035 ms	HTTP/1.1	cloudflare

See the visual redirect chain in the HTTP Probe tab →

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

URL Variants

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

REVIEW

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

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.iisd.org/

200https://iisd.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://iisd.org/ → https://iisd.org:443/

Consistent

B

HTTP Probe Timing

Total 826 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

545 ms

TCP Connect

93 ms

TLS Handshake

95 ms

Time to First Byte

826 ms

Total Time

827 ms

Connection waterfall

DNS Lookup 545 ms TCP Connect 93 ms TLS Handshake 95 ms Server Processing 93 ms Content Transfer 0 ms

B

TLS Certificate Expiry & Recommendations

272 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

272

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

A

DNS Records

2 A records, 560 ms lookup

PASS

2 A records, 560 ms lookup

Resolves to 2 IPv4 address(es)

Got: 3.97.150.156, 16.52.20.27

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: ns-1403.awsdns-47.org, ns-1958.awsdns-52.co.uk, ns-690.awsdns-22.net, ns-94.awsdns-11.com

1 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 is slow (560 ms)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Got: 560 ms

A	3.97.150.156, 16.52.20.27
AAAA	—
CNAME	—
NS	ns-1403.awsdns-47.org, ns-1958.awsdns-52.co.uk, ns-690.awsdns-22.net, ns-94.awsdns-11.com
MX	0 iisd-org.mail.protection.outlook.com
TXT	google-site-verification=pU2oPXbSX8QAbWAO4bGi8RxpBWOglTrdmSAlKEySM08 google-site-verification=tTUl9YUYmtt74AEld67URmrmG2Pu7ZvNDMwL3YIv4f8 pardot934563=64317e550fb5687d1525a84a6a0ac02b47fae13bb75b27f0353d926a35970bb1 SPF v=spf1 include:spf.protection.outlook.com include:servers.mcsv.net include:aspmx...
CAA	Lookup not available with standard resolver

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

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+

Crawlability

robots.txt present, sitemap with 5 URLs

PASS

robots.txt present, sitemap with 5 URLs

robots.txt is present

Got: 1636 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 5 entries

Sitemap index with 5 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 1636 B Sitemaps referenced 1 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

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/add/
Disallow: /search/
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/add/
Disallow: /index.php/search/
Disallow: /index.php/user/password/
Disallow: /index.php/user/register/
Disallow: /index.php/user/login/
Disallow: /index.php/user/logout/

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

sitemap.xml 200 OK

Type Sitemap Index URLs 5 entries Valid XML Yes

Child Sitemaps:

A

Domain Intelligence

iisd.org — via Amazon Registrar, Inc., 30 years, 3 months old, hosted on AWS

PASS

iisd.org — via Amazon Registrar, Inc., 30 years, 3 months old, hosted on AWS

Domain expires in 36 days

Consider enabling auto-renewal to prevent accidental expiration.

Got: Expires May 29, 2026

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: AWS

Got: AS16509

Domain expiry

EXPIRED

May 29, 2026

SSL certificate

272 days

Issued by Amazon

Domain age

30 years, 3 months

Registered May 30, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

16.52.20.27

Registrar

Amazon Registrar, Inc.

Unlocked 4 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Domain has EXPIRED — renew immediately to avoid total site outage
Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar Amazon Registrar, Inc.

Created May 30, 1996 (30 years, 3 months ago)

Expires May 29, 2026 (1 months)

Last Updated April 29, 2025

Name Servers ns-1403.awsdns-47.org, ns-1958.awsdns-52.co.uk, ns-690.awsdns-22.net, ns-94.awsdns-11.com

DNSSEC Not enabled

Hosting

IP Address 16.52.20.27

ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)

Provider AWS

Data source: rdap (0.4s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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