Infrastructure - https://mailchi.mp BeaverCheck Audit

F

Crawlability

Action

robots.txt present, sitemap with 0 URLs

FIX

robots.txt present, sitemap with 0 URLs

robots.txt is present

Got: 138 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 contains invalid XML

Search engines may not be able to parse the sitemap. Fix XML validation errors.

sitemap.xml is empty — no URLs found

An empty sitemap provides no value. Add <url> entries for your pages.

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

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more ▾

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

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 138 B Sitemaps referenced 0 User-agents facebookexternalhit, LinkedInBot, *, Twitterbot Blocking Yes — all crawlers blocked

User-agent: Twitterbot
Disallow:

User-agent: facebookexternalhit
Disallow:

User-agent: LinkedInBot
Disallow:

User-agent: *
Disallow: /

sitemap.xml 200 OK

Type URL Set URLs 0 entries Valid XML No

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

70 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

70

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

Akamai

REVIEW

Akamai

Site is served via Akamai CDN

Got: server header

CDN Detected: Akamai

Provider Akamai Evidence server header

A

DNS Records

1 A records, 6 ms lookup

PASS

1 A records, 6 ms lookup

Resolves to 1 IPv4 address(es)

Got: 104.92.231.83

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

6 nameserver(s) configured

Got: a6-66.akam.net, a1-205.akam.net, a5-65.akam.net, a7-66.akam.net, a4-65.akam.net, a14-66.akam.net

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.

No SPF record found in TXT records

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

DNS resolution time: 6 ms

Got: 6 ms

A	104.92.231.83
AAAA	—
CNAME	—
NS	a6-66.akam.net, a1-205.akam.net, a5-65.akam.net, a7-66.akam.net, a4-65.akam.net, a14-66.akam.net
MX	0
TXT	_toin9huu589agyp4696chh14he1uapf mc9b7rzy3grxm948y2xcgz5dxr7kd240 _dnsauth= 2bdfn16j7yq94p9z8lm6txdktwk00rb8 _sntdcyrz33vmvon0cxroi35i3jukxil google-site-verification=-zv1gucS2cm8NrS-dbqQIUm-e6n28RSFjC1llEK3tMU
CAA	Lookup not available with standard resolver

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

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)

A

Redirect Chain

1 redirect(s), 610 ms total

PASS

1 redirect(s), 610 ms total

Single redirect

Got: https://mailchi.mp → https://mailchimp.com/ (301)

Redirect overhead: 610 ms total

Got: 610 ms

Cross-domain redirect detected

https://mailchi.mp

13 ms · HTTP/1.1

301

https://mailchimp.com/

597 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://mailchi.mp	301	13 ms	HTTP/1.1	AkamaiGHost
2	https://mailchimp.com/	200	597 ms	HTTP/1.1	istio-envoy

See the visual redirect chain in the HTTP Probe tab →

A

URL Variants

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

PASS

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

HTTP→HTTPS redirect uses 302 instead of 301

Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

https://www.mailchi.mp/

200https://mailchi.mp/

HTTP → HTTPS

302http://mailchi.mp/ → https://mailchi.mp/

Use 301 (permanent) instead of 302 (temporary)

A+

HTTP Probe Timing

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

PASS

DNS Lookup

5 ms

TCP Connect

1 ms

TLS Handshake

4 ms

Time to First Byte

12 ms

Total Time

12 ms

Connection waterfall

DNS Lookup 5 ms TCP Connect 1 ms TLS Handshake 4 ms Server Processing 2 ms Content Transfer 0 ms

Domain Intelligence

Domain intelligence data not available

INFO

Domain intelligence data not available

RDAP and WHOIS lookup both failed