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

DNSSEC

Unsigned (DNSSEC not deployed)

REVIEW

Unsigned (DNSSEC not deployed)

DNSSEC is not deployed

The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).

B

CAA Records

No CAA records (any CA may issue certificates)

REVIEW

No CAA records (any CA may issue certificates)

No CAA records published

Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.

B

Reverse DNS

0/1 IPs match cert SAN

REVIEW

0/1 IPs match cert SAN

PTR for 66.29.144.183 does not match any cert SAN: 66-29-144-183.cprapid.com

Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.

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

200https://localxlist.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

B

TLS Certificate Expiry & Recommendations

78 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

78

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 Cache Observability

No CDN cache-status headers in the response

REVIEW

No CDN cache-status headers in the response

Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.

B

Operational Status Page

No status page link detected

REVIEW

No status page link detected

No operational status page link detected

Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.

B

Health Check Endpoint

No conventional health endpoint found

REVIEW

No conventional health endpoint found

Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.

A

DNS Records

1 A records, 508 ms lookup

PASS

1 A records, 508 ms lookup

Resolves to 1 IPv4 address(es)

Got: 66.29.144.183

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: ns2.findbare.com, ns1.findbare.com

1 mail exchanger(s) configured

SPF record present in TXT

DNS resolution is slow (508 ms)

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

Got: 508 ms

A	66.29.144.183
AAAA	—
CNAME	—
NS	ns2.findbare.com, ns1.findbare.com
MX	0 mail.localxlist.org
TXT	google-site-verification=S8xxfwoDtJ2Hoc16U2oN3S3vPaQGeOGYAyGzYxqiykk SPF v=spf1 ip4:66.29.144.183 ip4:159.198.35.172 ip4:66.29.156.3 ip4:66.29.144.186 ip...
CAA	Lookup not available with standard resolver

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

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+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A+

Multi-Resolver DNS Speed

Mean 24ms across 3 resolvers (spread 40ms)

PASS

Mean 24ms across 3 resolvers (spread 40ms)

Google: 11ms

Got: 11ms via 8.8.8.8:53

Cloudflare: 11ms

Got: 11ms via 1.1.1.1:53

Quad9: 51ms

Got: 51ms via 9.9.9.9:53

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://localxlist.org

https://localxlist.org

720 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://localxlist.org	200	720 ms	HTTP/1.1	nginx

A+

Crawlability

robots.txt present, sitemap with 20 URLs

PASS

robots.txt present, sitemap with 20 URLs

robots.txt is present

Got: 206 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 20 entries

Sitemap index with 20 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

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

User-Agent: *
Allow: /
Disallow: /api/*
Disallow: /forgot-password
Disallow: /forgot-verification
Disallow: /reset-password
Disallow: /signup-verification

Sitemap: https://localxlist.org/sitemap-index.xml

sitemap.xml 200 OK

Type Sitemap Index URLs 20 entries Valid XML Yes

Child Sitemaps:

A+

Domain Intelligence

localxlist.org — via NameCheap, Inc., 7 years, 8 months old, hosted on Namecheap

PASS

localxlist.org — via NameCheap, Inc., 7 years, 8 months old, hosted on Namecheap

Domain registered until Jan 1, 2027 (4 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: NameCheap, 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: Namecheap

Got: AS22612

Domain expiry

128 days

January 1, 2027

SSL certificate

78 days

Issued by Let's Encrypt

Domain age

7 years, 8 months

Registered January 1, 2019

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Namecheap

ASN AS22612

66.29.144.183

Registrar

NameCheap, Inc.

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 NameCheap, Inc.

Created January 1, 2019 (7 years, 8 months ago)

Expires January 1, 2027 (4 months)

Last Updated August 12, 2026

Name Servers ns1.findbare.com, ns2.findbare.com

DNSSEC Not enabled

Hosting

IP Address 66.29.144.183

ASN AS22612 (NAMECHEAP-NET - Namecheap, Inc., US)

Provider Namecheap

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

PASS

DNS Lookup

36 ms

TCP Connect

24 ms

TLS Handshake

27 ms

Time to First Byte

325 ms

Total Time

670 ms

Connection waterfall

DNS Lookup 36 ms TCP Connect 24 ms TLS Handshake 27 ms Server Processing 238 ms Content Transfer 345 ms