Infrastructure - https://www.maddox.com BeaverCheck Audit

B

DNS Records

1 A records, 28 ms lookup

REVIEW

1 A records, 28 ms lookup

Resolves to 1 IPv4 address(es)

Got: 198.202.211.1

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

Has 1 IPv6 (AAAA) record(s)

Got: 2620:cb:2000::1

CNAME record at zone apex

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Got: cdn.webflow.com

2 nameserver(s) configured

Got: journey.ns.cloudflare.com, lamar.ns.cloudflare.com

No MX records — email not configured via DNS

No SPF record found in TXT records

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

DNS resolution time: 28 ms

Got: 28 ms

A	198.202.211.1
AAAA	2620:cb:2000::1
CNAME	cdn.webflow.com
NS	journey.ns.cloudflare.com, lamar.ns.cloudflare.com
MX	—
TXT	—
CAA	Lookup not available with standard resolver

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

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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)

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/2 IPs match cert SAN

REVIEW

0/2 IPs match cert SAN

PTR lookup failed for 198.202.211.1: lookup 198.202.211.1: 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 2620:cb:2000::1: lookup 2620:cb:2000::1: 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

TLS Certificate Expiry & Recommendations

83 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

83

days left

0d 30d 60d 90d+

Recommended actions

Add includeSubDomains to the HSTS directive
Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
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

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+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

CNAME does not point at a known takeover-able service

A+

Multi-Resolver DNS Speed

Mean 37ms across 3 resolvers (spread 31ms)

PASS

Mean 37ms across 3 resolvers (spread 31ms)

Cloudflare: 24ms

Got: 24ms via 1.1.1.1:53

Google: 32ms

Got: 32ms via 8.8.8.8:53

Quad9: 55ms

Got: 55ms via 9.9.9.9:53

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://www.maddox.com

https://www.maddox.com

27 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://www.maddox.com	200	27 ms	HTTP/1.1	cloudflare

A+

IPv6 Readiness

IPv6 reachable (16 ms)

PASS

IPv6 reachable (16 ms)

IPv6 is configured and reachable at 2620:cb:2000::1

Got: 16 ms connect

IPv6 Ready

AAAA Records 2620:cb:2000::1 Connection Reachable (16 ms)

A+

Crawlability

robots.txt present, sitemap with 298 URLs

PASS

robots.txt present, sitemap with 298 URLs

robots.txt is present

Got: 67 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 298 entries

robots.txt references sitemap

robots.txt 200 OK

Size 67 B Sitemaps referenced 1 User-agents * Allow: / Blocking No — crawling allowed

User-agent: * Allow: /

Sitemap: https://www.maddox.com/sitemap.xml

sitemap.xml 200 OK

Type URL Set URLs 298 entries Valid XML Yes

Sample URLs:

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: www)

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

200https://www.maddox.com/

301https://maddox.com/

Preferred variant: www

HTTP → HTTPS

301http://www.maddox.com/ → https://www.maddox.com/

Consistent

A+

Domain Intelligence

maddox.com — via Cloudflare, Inc., 29 years, 8 months old

PASS

maddox.com — via Cloudflare, Inc., 29 years, 8 months old

Domain registered until Feb 28, 2034 (7 years, 6 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: Cloudflare, 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

2716 days

February 28, 2034

SSL certificate

83 days

Issued by Google Trust Services

Domain age

29 years, 8 months

Registered May 28, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2620:cb:2000::1

Registrar

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

Created May 28, 1997 (29 years, 8 months ago)

Expires February 28, 2034 (7 years, 6 months)

Last Updated February 29, 2024

Name Servers haley.ns.cloudflare.com, steven.ns.cloudflare.com

DNSSEC Not enabled

Hosting

IP Address 2620:cb:2000::1

Data source: rdap (0.2s)

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

PASS

DNS Lookup

41 ms

TCP Connect

1 ms

TLS Handshake

6 ms

Time to First Byte

108 ms

Total Time

109 ms

Connection waterfall

DNS Lookup 41 ms TCP Connect 1 ms TLS Handshake 6 ms Server Processing 60 ms Content Transfer 1 ms

A+

CDN & Delivery

Document on Cloudflare; assets also on AWS CloudFront, Akamai

PASS

Document on Cloudflare; assets also on AWS CloudFront, Akamai

Document is served via Cloudflare CDN (edge: MAD)

Got: cf-ray: a3e568e0ba8fec96-MAD

CDN cache status: HIT

Assets on Cloudflare: cdn.prod.website-files.com (assets: 164), cache HIT

Got: cf-ray: a3e56a90ccfad482-CDG

Assets on Cloudflare: cdn.jsdelivr.net (assets: 4), cache HIT

Got: delegation cdn.jsdelivr.net.cdn.cloudflare.net

Assets on AWS CloudFront: s.adroll.com (assets: 3), cache Hit from cloudfront

Got: delegation d1qug1xf2dk5z6.cloudfront.net

Assets on Akamai: snap.licdn.com (assets: 3)

Got: delegation od.linkedin.edgesuite.net

Assets on Cloudflare: unpkg.com (assets: 3), cache HIT

Got: cf-ray: a3e56a90fb11d08f-CDG

Document served via CDN: Cloudflare

Provider Cloudflare Cache Status HIT Evidence cf-ray: a3e568e0ba8fec96-MAD

Asset hosts on a CDN

cdn.prod.website-files.com — Cloudflare · assets: 164 · Cache Status: HIT
cdn.jsdelivr.net — Cloudflare · assets: 4 · Cache Status: HIT
s.adroll.com — AWS CloudFront · assets: 3 · Cache Status: Hit from cloudfront
snap.licdn.com — Akamai · assets: 3
unpkg.com — Cloudflare · assets: 3 · Cache Status: HIT

Other asset hosts

tags.srv.stackadapt.com — assets: 3 · AWS
www.googletagmanager.com — assets: 3 · Google
bat.bing.com — assets: 2 · below probe threshold
connect.facebook.net — assets: 2 · below probe threshold
opps-widget.getwarmly.com — assets: 2 · below probe threshold
57052.tctm.co — assets: 1 · below probe threshold
analytics.ahrefs.com — assets: 1 · below probe threshold
b2bjsstore.s3.us-west-2.amazonaws.com — assets: 1 · below probe threshold
bat.bing.net — assets: 1 · below probe threshold
bzrcdn.openai.com — assets: 1 · below probe threshold
d.adroll.com — assets: 1 · below probe threshold
d3e54v103j8qbb.cloudfront.net — assets: 1 · below probe threshold
js.hs-analytics.net — assets: 1 · below probe threshold
js.hs-banner.com — assets: 1 · below probe threshold
js.hs-scripts.com — assets: 1 · below probe threshold
js.hsadspixel.net — assets: 1 · below probe threshold
js.hscollectedforms.net — assets: 1 · below probe threshold
js.hsforms.net — assets: 1 · below probe threshold
js.usemessages.com — assets: 1 · below probe threshold
js.zi-scripts.com — assets: 1 · below probe threshold
s.yimg.com — assets: 1 · below probe threshold
scripts.clarity.ms — assets: 1 · below probe threshold
sp.analytics.yahoo.com — assets: 1 · below probe threshold
www.clarity.ms — assets: 1 · below probe threshold
www.google-analytics.com — assets: 1 · below probe threshold
www.google.com — assets: 1 · below probe threshold
www.gstatic.com — assets: 1 · below probe threshold
www.redditstatic.com — assets: 1 · below probe threshold

A+

CDN Cache Observability

Cache state: HIT

PASS

Cache state: HIT

CDN cache state observable via 2 header(s)

Got: age=228832, cf-cache-status=HIT