Infrastructure - https://www.cutsclothing.com/en-ng/ 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: 23.227.38.74

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

Has 1 IPv6 (AAAA) record(s)

Got: 2620:127:f00f:e::

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: shops.myshopify.com

No NS records found

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	23.227.38.74
AAAA	2620:127:f00f:e::
CNAME	shops.myshopify.com
NS	—
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

Reverse DNS

0/2 IPs match cert SAN

REVIEW

0/2 IPs match cert SAN

PTR for 23.227.38.74 does not match any cert SAN: shops.myshopify.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.

PTR lookup failed for 2620:127:f00f:e::: lookup 2620:127:f00f:e::: 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

Redirect Chain

1 redirect(s), 1020 ms total

REVIEW

1 redirect(s), 1020 ms total

Single redirect

Got: https://www.cutsclothing.com/en-ng/ → https://www.cutsclothing.com/en-es/ (302)

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://www.cutsclothing.com/en-ng/

Redirect overhead: 1020 ms total

Got: 1020 ms

https://www.cutsclothing.com/en-ng/

564 ms · HTTP/1.1

302

https://www.cutsclothing.com/en-es/

457 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://www.cutsclothing.com/en-ng/	302	564 ms	HTTP/1.1	cloudflare
2	https://www.cutsclothing.com/en-es/	200	457 ms	HTTP/1.1	cloudflare

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

B

TLS Certificate Expiry & Recommendations

86 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

86

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

CDN & Delivery

Document on Shopify; assets also on Cloudflare

REVIEW

Document on Shopify; assets also on Cloudflare

Document is served via Shopify CDN

Got: delegation shops.myshopify.com

Assets on Cloudflare: cdn.shopify.com (assets: 17), cache HIT

Got: cf-ray: a52c46a40b59735b-CDG

Document served via CDN: Shopify

Provider Shopify Evidence delegation shops.myshopify.com

Asset hosts on a CDN

cdn.shopify.com — Cloudflare · assets: 17 · Cache Status: HIT

Other asset hosts

cdn.fuego.io — assets: 2 · below probe threshold
cdn.jsdelivr.net — assets: 2 · below probe threshold
fonts.googleapis.com — assets: 2 · below probe threshold
cdn.sdk.veeperapp.com — assets: 1 · below probe threshold
cdnjs.cloudflare.com — assets: 1 · below probe threshold
storefront-direct-upload.s3.amazonaws.com — assets: 1 · below probe threshold
www.heyplaybook.com — assets: 1 · below probe threshold

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+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

CNAME does not point at a known takeover-able service

A

CAA Records

issue: digicert.com, globalsign.com, letsencrypt.org, pki.goog, ssl.com

PASS

issue: digicert.com, globalsign.com, letsencrypt.org, pki.goog, ssl.com

CAA issue tag present — authorized CA(s): digicert.com, globalsign.com, letsencrypt.org, pki.goog, ssl.com

No CAA iodef tag — won't be notified of failed issuance attempts

Add `0 iodef "mailto:security@example.com"` to receive notifications when a CA refuses issuance because it doesn't match your CAA policy. Useful signal for detecting issuance attempts by unauthorized CAs.

A+

Multi-Resolver DNS Speed

Mean 35ms across 3 resolvers (spread 22ms)

PASS

Mean 35ms across 3 resolvers (spread 22ms)

Cloudflare: 26ms

Got: 26ms via 1.1.1.1:53

Google: 32ms

Got: 32ms via 8.8.8.8:53

Quad9: 48ms

Got: 48ms via 9.9.9.9:53

A+

IPv6 Readiness

IPv6 reachable (17 ms)

PASS

IPv6 reachable (17 ms)

IPv6 is configured and reachable at 2620:127:f00f:e::

Got: 17 ms connect

IPv6 Ready

AAAA Records 2620:127:f00f:e:: Connection Reachable (17 ms)

A+

Crawlability

robots.txt present, sitemap with 19 URLs

PASS

robots.txt present, sitemap with 19 URLs

robots.txt is present

Got: 460 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 19 entries

Sitemap index with 19 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 460 B Sitemaps referenced 1 User-agents Pinterest, *, adsbot-google Blocking No — crawling allowed

User-agent: *
    Disallow: /admin
    Disallow: /cart
    Disallow: /orders
    Disallow: /checkouts/
    Disallow: /checkout
    Disallow: /carts
    Disallow: /account
    Sitemap: https://www.cutsclothing.com/sitemap.xml

    # Google adsbot ignores robots.txt unless specifically named!
    User-agent: adsbot-google
    Disallow: /checkouts/
    Disallow: /checkout
    Disallow: /carts
    Disallow: /orders

    User-agent: Pinterest
    Crawl-delay: 1

sitemap.xml 200 OK

Type Sitemap Index URLs 19 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: www)

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

200https://www.cutsclothing.com/en-ng/

301https://cutsclothing.com/en-ng/

Preferred variant: www

Trailing Slash

200https://www.cutsclothing.com/en-ng/

302https://www.cutsclothing.com/en-ng

HTTP → HTTPS

301http://www.cutsclothing.com/en-ng/ → https://www.cutsclothing.com/en-ng/

Consistent

A+

Domain Intelligence

cutsclothing.com — via GoDaddy.com, LLC, 13 years, 4 months old

PASS

cutsclothing.com — via GoDaddy.com, LLC, 13 years, 4 months old

Domain registered until Aug 19, 2032 (5 years, 10 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: GoDaddy.com, 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.

Domain expiry

2111 days

August 19, 2032

SSL certificate

86 days

Issued by Let's Encrypt

Domain age

13 years, 4 months

Registered August 19, 2013

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2620:127:f00f:5::

Registrar

GoDaddy.com, LLC

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 GoDaddy.com, LLC

Created August 19, 2013 (13 years, 4 months ago)

Expires August 19, 2032 (5 years, 10 months)

Last Updated February 1, 2023

Name Servers pdns13.domaincontrol.com, pdns14.domaincontrol.com

DNSSEC Not enabled

Hosting

IP Address 2620:127:f00f:5::

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

PASS

DNS Lookup

41 ms

TCP Connect

17 ms

TLS Handshake

25 ms

Time to First Byte

455 ms

Total Time

455 ms

Connection waterfall

DNS Lookup 41 ms TCP Connect 17 ms TLS Handshake 25 ms Server Processing 373 ms Content Transfer 0 ms