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

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.schneier.com/

200https://schneier.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://schneier.com/ → https://schneier.com/

Consistent

B

TLS Certificate Expiry & Recommendations

82 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

82

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

A+

DNS Records

2 A records, 139 ms lookup

PASS

2 A records, 139 ms lookup

Resolves to 2 IPv4 address(es)

Got: 199.16.172.203, 199.16.173.239

No IPv6 (AAAA) records

2 nameserver(s) configured

Got: ns79.worldnic.com, ns80.worldnic.com

2 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: 139 ms

Got: 139 ms

A	199.16.172.203, 199.16.173.239
AAAA	—
CNAME	—
NS	ns79.worldnic.com, ns80.worldnic.com
MX	10 mx1.emailsrvr.com 20 mx2.emailsrvr.com
TXT	SPF v=spf1 a include:emailsrvr.com include:servers.mcsv.net ip4:204.11.247.92 ip4:20...
CAA	Lookup not available with standard resolver

Resolved in 139 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

Redirect Chain

1 redirect(s), 296 ms total

PASS

1 redirect(s), 296 ms total

Single redirect

Got: https://schneier.com → https://www.schneier.com/ (301)

WWW normalization redirect

https://schneier.com

33 ms · HTTP/1.1

301

https://www.schneier.com/

263 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://schneier.com	301	33 ms	HTTP/1.1	nginx
2	https://www.schneier.com/	200	263 ms	HTTP/1.1	nginx

See the visual redirect chain in the HTTP Probe tab →

A+

Crawlability

robots.txt present, sitemap with 37 URLs

PASS

robots.txt present, sitemap with 37 URLs

robots.txt is present

Got: 600 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 37 entries

Sitemap index with 37 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

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

User-agent: *
Disallow: /wp-content/uploads/wc-logs/
Disallow: /wp-content/uploads/woocommerce_transient_files/
Disallow: /wp-content/uploads/woocommerce_uploads/
Disallow: /*?add-to-cart=
Disallow: /*?*add-to-cart=
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

# START WPFORMS BLOCK
# ---------------------------
User-agent: *
Disallow: /wp-content/uploads/wpforms/
# ---------------------------
# END WPFORMS BLOCK

# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://www.schneier.com/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK

sitemap.xml 200 OK

Type Sitemap Index URLs 37 entries Valid XML Yes

Child Sitemaps:

A+

Domain Intelligence

schneier.com — via Network Solutions, LLC, 27 years, 3 months old, hosted on WordPress.com (Automattic)

PASS

schneier.com — via Network Solutions, LLC, 27 years, 3 months old, hosted on WordPress.com (Automattic)

Domain registered until May 22, 2029 (3 years, 1 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: WordPress.com (Automattic)

Got: AS2635

Domain expiry

1071 days

May 22, 2029

SSL certificate

82 days

Issued by Google Trust Services

Domain age

27 years, 3 months

Registered May 22, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

WordPress.com (Automattic)

ASN AS2635

199.16.173.239

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 May 22, 1999 (27 years, 3 months ago)

Expires May 22, 2029 (3 years, 1 months)

Last Updated July 10, 2023

Name Servers ns79.worldnic.com, ns80.worldnic.com

DNSSEC Not enabled

Hosting

IP Address 199.16.173.239

ASN AS2635 (AUTOMATTIC - Automattic, Inc, US)

Provider WordPress.com (Automattic)

Data source: rdap (0.3s)

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

PASS

DNS Lookup

126 ms

TCP Connect

0 ms

TLS Handshake

3 ms

Time to First Byte

156 ms

Total Time

156 ms

Connection waterfall

DNS Lookup 126 ms TCP Connect 0 ms TLS Handshake 3 ms Server Processing 27 ms Content Transfer 0 ms