Infrastructure - https://wilsoncenter.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.

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

C

Crawlability

Action

robots.txt present, sitemap with 63 URLs

REVIEW

robots.txt present, sitemap with 63 URLs

robots.txt is present

Got: 26 bytes

robots.txt blocks all crawlers

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 63 entries

Sitemap index with 63 child sitemaps

robots.txt does not reference a sitemap

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.

Learn more ▾

Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.

Source: Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK

Size 26 B Sitemaps referenced 0 User-agents * Blocking Yes — all crawlers blocked

User-agent: *
Disallow: /

sitemap.xml 200 OK

Type Sitemap Index URLs 63 entries Valid XML Yes

Child Sitemaps:

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.wilsoncenter.org/

200https://wilsoncenter.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://wilsoncenter.org/ → https://wilsoncenter.org/

Consistent

B

TLS Certificate Expiry & Recommendations

75 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

75

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

1 A records, 400 ms lookup

PASS

1 A records, 400 ms lookup

Resolves to 1 IPv4 address(es)

Got: 34.226.46.235

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

2 nameserver(s) configured

Got: ns16.worldnic.com, ns15.worldnic.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 (400 ms)

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

Got: 400 ms

A	34.226.46.235
AAAA	—
CNAME	—
NS	ns16.worldnic.com, ns15.worldnic.com
MX	10 wilsoncenter-org.mail.protection.outlook.com
TXT	asv=bce0d5117d8e725c84fd464dd507d048 apple-domain-verification=7I2e4WZ83GzMf2G5 google-site-verification=8sSJVfFjvqGdyiqIbHL6brg_3oxIFFVQnM1RM53dGWM MS=B74CD36447FBF0D075748CB80B3FFAF34038238D SPF v=spf1 ip4:205.201.242.126/25 ip4:72.35.12.4 ip4:208.70.129.4 ip4:151.101.2.216 ... adobe-idp-site-verification=dca453295de8cea4c6ce112e2be1515832a849c20b35720efbe6... bce0d5117d8e725c84fd464dd507d048 bcYGplnE16/WkKDiTkujx3z0quyvWRjAqxqFofs1Rl2M9eEg51SL+FI9wcQHwAvTPeK2HPTIL+H460Nl... ZOOM_verify_PvipHSXSYEnHQHmpXqHUK1
CAA	Lookup not available with standard resolver

Resolved in 400 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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

Redirect Chain

1 redirect(s), 394 ms total

PASS

1 redirect(s), 394 ms total

Single redirect

Got: https://wilsoncenter.org → https://www.wilsoncenter.org/ (302)

WWW normalization redirect

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://wilsoncenter.org

https://wilsoncenter.org

299 ms · HTTP/1.1

302

https://www.wilsoncenter.org/

95 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://wilsoncenter.org	302	299 ms	HTTP/1.1
2	https://www.wilsoncenter.org/	200	95 ms	HTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

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

A+

Domain Intelligence

wilsoncenter.org — via Network Solutions, LLC, 26 years, 11 months old, hosted on AWS

PASS

wilsoncenter.org — via Network Solutions, LLC, 26 years, 11 months old, hosted on AWS

Domain registered until Sep 13, 2029 (3 years, 5 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: Network Solutions, LLC

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

1186 days

September 13, 2029

SSL certificate

75 days

Issued by Let's Encrypt

Domain age

26 years, 11 months

Registered September 13, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

34.226.46.235

Registrar

Network Solutions, LLC

Unlocked 2 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 Network Solutions, LLC

Created September 13, 1999 (26 years, 11 months ago)

Expires September 13, 2029 (3 years, 5 months)

Last Updated March 25, 2024

Name Servers ns15.worldnic.com, ns16.worldnic.com

DNSSEC Not enabled

Hosting

IP Address 34.226.46.235

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

Provider AWS

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

PASS

DNS Lookup

146 ms

TCP Connect

99 ms

TLS Handshake

100 ms

Time to First Byte

444 ms

Total Time

444 ms

Connection waterfall

DNS Lookup 146 ms TCP Connect 99 ms TLS Handshake 100 ms Server Processing 99 ms Content Transfer 0 ms