Infrastructure - https://lithub.com BeaverCheck Audit

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

317 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

317

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

4 A records, 34 ms lookup

PASS

4 A records, 34 ms lookup

Resolves to 4 IPv4 address(es)

Got: 18.244.214.73, 18.244.214.95, 18.244.214.58, 18.244.214.74

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: ns-1082.awsdns-07.org, ns-1837.awsdns-37.co.uk, ns-416.awsdns-52.com, ns-739.awsdns-28.net

5 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: 34 ms

Got: 34 ms

A	18.244.214.73, 18.244.214.95, 18.244.214.58, 18.244.214.74
AAAA	—
CNAME	—
NS	ns-1082.awsdns-07.org, ns-1837.awsdns-37.co.uk, ns-416.awsdns-52.com, ns-739.awsdns-28.net
MX	1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt4.aspmx.l.google.com 10 alt3.aspmx.l.google.com
TXT	google-site-verification=E8si9z5cHt-5Q30_tFEPoKgfFwdsjdtzi6mdd7f-uC0 google-site-verification=_eiP8wKfxC54katxBeC2MyrY2wst8yM-cNjWWt1C-Ys klaviyo-site-verification=U5D8ER SPF v=spf1 a mx include:aspmx.sailthru.com include:servers.mcsv.net include:_spf.go... yahoo-verification-key=AE3PrmoGMiD1kC3LIQs71U0QbLWPSL165RY1rp9CLr4=
CAA	Lookup not available with standard resolver

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

No redirects — direct access

PASS

No redirects — direct access

Got: https://lithub.com

https://lithub.com

40 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://lithub.com	200	40 ms	HTTP/1.1	Pagely-ARES/1.22.2

A+

Crawlability

robots.txt present, sitemap with 21 URLs

PASS

robots.txt present, sitemap with 21 URLs

robots.txt is present

Got: 379 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 21 entries

Sitemap index with 21 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 379 B Sitemaps referenced 3 User-agents * Blocking No — crawling allowed

User-agent: *
Disallow: /wp-includes/
Disallow: /wp-login.php
Disallow: /wp-admin/*
Disallow: /wp-register.php
Disallow: /book-widget/*
Disallow: */tag/*
Disallow: *?s=*
Disallow: /search/*
Allow: /wp-admin/admin-ajax.php

Sitemap: https://lithub.com/wp-sitemap.xml
Sitemap: https://bookmarks.reviews/wp-sitemap.xml
Sitemap: https://crimereads.com/wp-sitemap.xml
crawl-delay: 10

sitemap.xml 200 OK

Type Sitemap Index URLs 21 entries Valid XML Yes

Child Sitemaps:

A+

URL Variants

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

PASS

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

www/non-www redirect configured correctly (preferred: non-www)

HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.lithub.com/

200https://lithub.com/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+

Domain Intelligence

lithub.com — via Wild West Domains, LLC, 12 years old, hosted on AWS

PASS

lithub.com — via Wild West Domains, LLC, 12 years old, hosted on AWS

Domain registered until Jun 6, 2029 (3 years, 2 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: Wild West Domains, 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

1089 days

June 6, 2029

SSL certificate

317 days

Issued by Amazon

Domain age

12 years

Registered June 6, 2014

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

18.244.214.73

Registrar

Wild West Domains, LLC

Unlocked 4 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 Wild West Domains, LLC

Created June 6, 2014 (12 years ago)

Expires June 6, 2029 (3 years, 2 months)

Last Updated April 6, 2024

Name Servers ns-1082.awsdns-07.org, ns-1837.awsdns-37.co.uk, ns-416.awsdns-52.com, ns-739.awsdns-28.net

DNSSEC Not enabled

Hosting

IP Address 18.244.214.73

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

Provider AWS

Data source: rdap (0.1s)

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

PASS

DNS Lookup

5 ms

TCP Connect

3 ms

TLS Handshake

6 ms

Time to First Byte

279 ms

Total Time

280 ms

Connection waterfall

DNS Lookup 5 ms TCP Connect 3 ms TLS Handshake 6 ms Server Processing 264 ms Content Transfer 1 ms

A

CDN & Delivery

AWS CloudFront (Miss from cloudfront)

PASS

AWS CloudFront (Miss from cloudfront)

Site is served via AWS CloudFront CDN (edge: SFO53-P4)

Got: x-amz-cf-id: y5TEokuVADhUa0GfyKuSdrFEfcefBBVnmj1jPSIyQKHcWpPF45AU1Q==

CDN cache status: Miss from cloudfront

CDN Detected: AWS CloudFront

Provider AWS CloudFront Cache Status Miss from cloudfront Evidence x-amz-cf-id: y5TEokuVADhUa0GfyKuSdrFEfcefBBVnmj1jPSIyQKHcWpPF45AU1Q==