Infrastructure - https://business-money.com BeaverCheck Audit

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.

C

Reverse DNS

Action

0/4 IPs match cert SAN

REVIEW

0/4 IPs match cert SAN

PTR lookup failed for 104.21.75.199: lookup 104.21.75.199: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

PTR lookup failed for 172.67.181.82: lookup 172.67.181.82: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

PTR lookup failed for 2606:4700:3036::6815:4bc7: lookup 2606:4700:3036::6815:4bc7: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

PTR lookup failed for 2606:4700:3035::ac43:b552: lookup 2606:4700:3035::ac43:b552: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

B

Crawlability

robots.txt present, no sitemap

REVIEW

robots.txt present, no sitemap

robots.txt is present

Got: 918 bytes

No sitemap.xml found

A sitemap helps search engines discover and index your pages more efficiently.

robots.txt does not reference a sitemap

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

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / 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 918 B Sitemaps referenced 0 User-agents *, YisouSpider, PetalBot, Bytespider, SemrushBot, Barkrowler, DotBot, Googlebot, AhrefsBot, MJ12bot, Baiduspider, SeekportBot, Bingbot Blocking No — crawling allowed

# GENERAL BOT RULES (limit load)

User-agent: *

Disallow: /wp-admin/

Disallow: /wp-login.php

Disallow: /cart/

Disallow: /checkout/

Disallow: /my-account/

Disallow: /?s=

Disallow: /wp-content/uploads/wc-logs/

Disallow: /wp-content/uploads/woocommerce_transient_files/

Allow: /wp-admin/admin-ajax.php

Crawl-delay: 10

# BLOCK ABUSIVE BOTS COMPLETELY

User-agent: AhrefsBot

Disallow: /

User-agent: YisouSpider

Disallow: /


User-agent: MJ12bot

Disallow: /


User-agent: Baiduspider

Disallow: /


User-agent: MJ12bot

Disallow: /


User-agent: PetalBot

Disallow: /


User-agent: Bytespider

Disallow: /


User-agent: SemrushBot

Disallow: /


User-agent: SeekportBot

Disallow: /


User-agent: Barkrowler

Disallow: /


User-agent: DotBot

Disallow: /


# GOOGLE AND BING SPECIFIC CRAWL RULES

User-agent: Googlebot

Disallow:

Crawl-delay: 50

User-agent: Bingbot

Disallow:

Crawl-delay: 50

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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.business-money.com/

200https://business-money.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://business-money.com/ → https://business-money.com/

Consistent

B

HTTP Probe Timing

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

REVIEW

DNS Lookup

11 ms

TCP Connect

2 ms

TLS Handshake

12 ms

Time to First Byte

1.45 s

Total Time

1.45 s

Connection waterfall

DNS Lookup 11 ms TCP Connect 2 ms TLS Handshake 12 ms Server Processing 1.42 s Content Transfer 0 ms

B

TLS Certificate Expiry & Recommendations

35 days until leaf cert expires — 2 issues to address

REVIEW

Certificate validity

35

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

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: connection error, /healthz: connection error, /ping: 404, /status: connection error.

A+

DNS Records

2 A records, 10 ms lookup

PASS

2 A records, 10 ms lookup

Resolves to 2 IPv4 address(es)

Got: 104.21.75.199, 172.67.181.82

Has 2 IPv6 (AAAA) record(s)

Got: 2606:4700:3036::6815:4bc7, 2606:4700:3035::ac43:b552

2 nameserver(s) configured

Got: nicole.ns.cloudflare.com, vern.ns.cloudflare.com

5 mail exchanger(s) configured

SPF record present in TXT

DNS resolution time: 10 ms

Got: 10 ms

A	104.21.75.199, 172.67.181.82
AAAA	2606:4700:3036::6815:4bc7, 2606:4700:3035::ac43:b552
CNAME	—
NS	nicole.ns.cloudflare.com, vern.ns.cloudflare.com
MX	1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com
TXT	brevo-code:39ead1ddce8d0d0ea1e7409b284719d7 SPF v=spf1 +ip4:45.84.57.114 +ip4:193.110.160.202 +include:_spf.google.com ~all
CAA	Lookup not available with standard resolver

Resolved in 10 ms

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A+

Multi-Resolver DNS Speed

Mean 12ms across 3 resolvers (spread 11ms)

PASS

Mean 12ms across 3 resolvers (spread 11ms)

Cloudflare: 5ms

Got: 5ms via 1.1.1.1:53

Quad9: 16ms

Got: 16ms via 9.9.9.9:53

Google: 15ms

Got: 15ms via 8.8.8.8:53

A

Redirect Chain

1 redirect(s), 809 ms total

PASS

1 redirect(s), 809 ms total

Single redirect

Got: https://business-money.com → https://www.business-money.com/ (301)

WWW normalization redirect

Redirect overhead: 809 ms total

Got: 809 ms

https://business-money.com

359 ms · HTTP/1.1

301

https://www.business-money.com/

450 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://business-money.com	301	359 ms	HTTP/1.1	cloudflare
2	https://www.business-money.com/	200	450 ms	HTTP/1.1	cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+

IPv6 Readiness

IPv6 reachable (3 ms)

PASS

IPv6 reachable (3 ms)

IPv6 is configured and reachable at 2606:4700:3036::6815:4bc7, 2606:4700:3035::ac43:b552

Got: 3 ms connect

IPv6 Ready

AAAA Records 2606:4700:3036::6815:4bc7, 2606:4700:3035::ac43:b552 Connection Reachable (3 ms)

A+

Domain Intelligence

business-money.com — via Tucows Domains Inc., 31 years old

PASS

business-money.com — via Tucows Domains Inc., 31 years old

Domain registered until Jan 8, 2028 (1 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: Tucows Domains 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.

Domain expiry

509 days

January 8, 2028

SSL certificate

35 days

Issued by Google Trust Services

Domain age

31 years

Registered January 9, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3035::ac43:b552

Registrar

Tucows Domains 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 Tucows Domains Inc.

Created January 9, 1996 (31 years ago)

Expires January 8, 2028 (1 years, 5 months)

Last Updated December 9, 2025

Name Servers nicole.ns.cloudflare.com, vern.ns.cloudflare.com

DNSSEC Not enabled

Hosting

IP Address 2606:4700:3035::ac43:b552

Data source: rdap (0.0s)

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

CDN & Delivery

Cloudflare (DYNAMIC)

PASS

Cloudflare (DYNAMIC)

Site is served via Cloudflare CDN (edge: EWR)

Got: cf-ray: a29b31e18a6ab96b-EWR

CDN cache status: DYNAMIC

CDN Detected: Cloudflare

Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a29b31e18a6ab96b-EWR

A+

CDN Cache Observability

Cache state: DYNAMIC

PASS

Cache state: DYNAMIC

CDN cache state observable via 1 header(s)

Got: cf-cache-status=DYNAMIC