Infrastructure - https://tuffdigitalmarketing.com BeaverCheck Audit

D

Multi-Resolver DNS Speed

Action

Mean 237ms across 3 resolvers (spread 574ms)

FIX

Mean 237ms across 3 resolvers (spread 574ms)

Quad9: 40ms

Got: 40ms via 9.9.9.9:53

Google: 58ms

Got: 58ms via 8.8.8.8:53

Cloudflare: 614ms

Got: 614ms via 1.1.1.1:53

High latency spread between resolvers: 574ms (min 40ms / max 614ms)

Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.

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 198.175.150.99 does not match any cert SAN: cloud212.cloudwebhosting.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

HTTP version does not redirect to HTTPS

Got: HTTP 0 Expected: 301 redirect to HTTPS

www / non-www

https://www.tuffdigitalmarketing.com/

200https://tuffdigitalmarketing.com/

HTTP → HTTPS

http://tuffdigitalmarketing.com/

HTTP version does not redirect to HTTPS

B

TLS Certificate Expiry & Recommendations

31 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

31

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

C

CDN & Delivery

Action

Assets on AWS CloudFront (host cdn.trustindex.io, 60 assets); document served directly from origin

REVIEW

Assets on AWS CloudFront (host cdn.trustindex.io, 60 assets); document served directly from origin

Document not behind existing CDN (AWS CloudFront serves the assets)

The page's subresources are delivered by AWS CloudFront (cdn.trustindex.io, 60 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.

Got: delegation dhtt2nmvztmk3.cloudfront.net

Assets on AWS CloudFront: cdn.trustindex.io (assets: 60), cache Hit from cloudfront

Got: delegation dhtt2nmvztmk3.cloudfront.net

Assets on Bunny CDN: fonts.bunny.net (assets: 4)

Got: delegation bunnyfonts.b-cdn.net

Assets on Cloudflare: widgets.leadconnectorhq.com (assets: 3), cache DYNAMIC

Got: cf-ray: a43c836dcdfbd911-EWR

Assets on a CDN, document is not: AWS CloudFront

Document origin not attributed

Asset hosts on a CDN

cdn.trustindex.io — AWS CloudFront · assets: 60 · Cache Status: Hit from cloudfront
fonts.bunny.net — Bunny CDN · assets: 4
widgets.leadconnectorhq.com — Cloudflare · assets: 3 · Cache Status: DYNAMIC

Other asset hosts

lh3.googleusercontent.com — assets: 10 · Google
www.googletagmanager.com — assets: 6 · Google
cdn.callrail.com — assets: 1 · below probe threshold
googleads.g.doubleclick.net — assets: 1 · below probe threshold
stcdn.leadconnectorhq.com — assets: 1 · below probe threshold

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

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

A

DNS Records

1 A records, 1235 ms lookup

PASS

1 A records, 1235 ms lookup

Resolves to 1 IPv4 address(es)

Got: 198.175.150.99

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

5 mail exchanger(s) configured

SPF record present in TXT

DNS resolution is slow (1235 ms)

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

Got: 1235 ms

A	198.175.150.99
AAAA	—
CNAME	—
NS	ns1.hostingbp.com, ns2.hostingbp.com
MX	1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 alt4.aspmx.l.google.com 10 alt3.aspmx.l.google.com
TXT	SPF v=spf1 +ip4:198.175.150.99 +include:_spf.cloudwebhosting.com +include:_spf.googl...
CAA	Lookup not available with standard resolver

Resolved in 1235 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+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://tuffdigitalmarketing.com

https://tuffdigitalmarketing.com

1330 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://tuffdigitalmarketing.com	200	1330 ms	HTTP/1.1	LiteSpeed

A+

Crawlability

robots.txt present, sitemap with 7 URLs

PASS

robots.txt present, sitemap with 7 URLs

robots.txt is present

Got: 804 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 7 entries

Sitemap index with 7 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 804 B Sitemaps referenced 1 User-agents *, GPTBot, ChatGPT-User, Google-Extended, GoogleOther, ClaudeBot, PerplexityBot Blocking No — crawling allowed

User-agent: GPTBot

Allow: /


User-agent: ChatGPT-User

Allow: /


User-agent: Google-Extended

Allow: /


User-agent: GoogleOther

Allow: /


User-agent: ClaudeBot

Allow: /


User-agent: PerplexityBot

Allow: /


User-agent: *

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

Allow: /wp-json/

Disallow: /wp-admin/

Disallow: /cgi-bin/

Disallow: /wp-includes/

Disallow: /author/

Disallow: /tag/

Disallow: /category/

Disallow: /feed/

Disallow: /search/

Disallow: /?s=

Disallow: /*?replytocom=

Disallow: /*?utm_*

Disallow: /*?ref=*

Disallow: /*?filter=

Disallow: /*&filter=

Disallow: /page/

Disallow: /wp-content/plugins/private-plugin-folder/

Disallow: /wp-content/themes/private-theme-folder/

Disallow: /wp-content/uploads/private/


Sitemap: https://tuffdigitalmarketing.com/sitemap_index.xml

sitemap.xml 200 OK

Type Sitemap Index URLs 7 entries Valid XML Yes

Child Sitemaps:

A

Domain Intelligence

tuffdigitalmarketing.com — via NameCheap, Inc., 7 years, 11 months old, hosted on NAMEHERO-KCDC - Name Hero, LLC, US

PASS

tuffdigitalmarketing.com — via NameCheap, Inc., 7 years, 11 months old, hosted on NAMEHERO-KCDC - Name Hero, LLC, US

Domain expires in 66 days

Consider enabling auto-renewal to prevent accidental expiration.

Got: Expires Dec 7, 2026

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: NAMEHERO-KCDC - Name Hero, LLC, US

Got: AS399250

Domain expiry

64 days

December 7, 2026

SSL certificate

31 days

Issued by Let's Encrypt

Domain age

7 years, 11 months

Registered December 7, 2018

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

NAMEHERO-KCDC - Name Hero, LLC, US

ASN AS399250

198.175.150.99

Registrar

NameCheap, Inc.

Unlocked 2 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Renew the domain or enable auto-renewal to prevent accidental expiry
Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar NameCheap, Inc.

Created December 7, 2018 (7 years, 11 months ago)

Expires December 7, 2026 (2 months)

Last Updated November 7, 2025

Name Servers ns1.hostingbp.com, ns2.hostingbp.com

DNSSEC Not enabled

Hosting

IP Address 198.175.150.99

ASN AS399250 (NAMEHERO-KCDC - Name Hero, LLC, US)

Provider NAMEHERO-KCDC - Name Hero, LLC, US

Data source: rdap (1.4s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

PASS

DNS Lookup

68 ms

TCP Connect

31 ms

TLS Handshake

35 ms

Time to First Byte

165 ms

Total Time

229 ms

Connection waterfall

DNS Lookup 68 ms TCP Connect 31 ms TLS Handshake 35 ms Server Processing 32 ms Content Transfer 64 ms