Infrastructure - https://wowshopper.com BeaverCheck Audit

D

CDN & Delivery

Action

No CDN (document or assets)

FIX

No CDN (document or assets)

Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.

No CDN (document or assets)

Consider using a CDN to improve global delivery speed and reduce origin load.

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 74.208.119.121 does not match any cert SAN: mail.aiyagroup.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

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

200https://www.wowshopper.com/

200https://wowshopper.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

C

TLS Certificate Expiry & Recommendations

Action

15 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

15

days left

0d 30d 60d 90d+

Renew soon — under 30 days remaining

Recommended actions

Renew certificate — 15 days remaining
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 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.

A+

DNS Records

1 A records, 30 ms lookup

PASS

1 A records, 30 ms lookup

Resolves to 1 IPv4 address(es)

Got: 74.208.119.121

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: ns1032.ui-dns.biz, ns1115.ui-dns.de, ns1114.ui-dns.com, ns1043.ui-dns.org

1 mail exchanger(s) configured

SPF record present in TXT

DNS resolution time: 30 ms

Got: 30 ms

A	74.208.119.121
AAAA	—
CNAME	—
NS	ns1032.ui-dns.biz, ns1115.ui-dns.de, ns1114.ui-dns.com, ns1043.ui-dns.org
MX	10 mail.wowshopper.com
TXT	SPF v=spf1 ip4:74.208.119.121 include:_spf.google.com ~all
CAA	Lookup not available with standard resolver

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

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A+

Multi-Resolver DNS Speed

Mean 20ms across 3 resolvers (spread 38ms)

PASS

Mean 20ms across 3 resolvers (spread 38ms)

Quad9: 1ms

Got: 1ms via 9.9.9.9:53

Google: 20ms

Got: 20ms via 8.8.8.8:53

Cloudflare: 39ms

Got: 39ms via 1.1.1.1:53

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://wowshopper.com

https://wowshopper.com

387 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://wowshopper.com	200	387 ms	HTTP/1.1	Apache

A+

Crawlability

robots.txt present, sitemap with 21 URLs

PASS

robots.txt present, sitemap with 21 URLs

robots.txt is present

Got: 3074 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 3074 B Sitemaps referenced 1 User-agents Applebot-Extended, Meta-ExternalAgent, Reflectionbot, Googlebot, YandexBot, ChatGPT-User, PerplexityBot, xAI-Search, Bingbot, Googlebot-Image, *, Google-Extended, Cohere-ai, Bytespider, GPTBot, Claude-Web, Grok, Google-Store-Bot, Slurp, DuckDuckBot, Applebot, anthropic-ai Blocking No — crawling allowed

User-Agent: *
Allow: /
Allow: /categories/
Allow: /brands/
Allow: /products/
Allow: /bundles/
Allow: /bundles
Allow: /riderclinic/
Allow: /specs/
Allow: /ride/
Allow: /sizing-guide
Allow: /showroom
Allow: /catalog
Allow: /catalog-log/
Allow: /about
Allow: /media
Allow: /contact-us
Allow: /shipping-policy
Allow: /returns-and-warranty
Allow: /privacy-policy
Allow: /terms-of-service
Allow: /ada-compliance
Allow: /google-shopping.xml
Allow: /feeds/
Allow: /api/feeds/
Allow: /api/bundles
Allow: /api/bundles/
Allow: /api/vehicles/specs
Allow: /llms.txt
Allow: /.well-known/
Disallow: /api/
Disallow: /admin/
Disallow: /cart
Disallow: /checkout
Disallow: /*.md$
Disallow: /*.markdown$
Disallow: /docs/

# ==============================================================================
# AI Shopping Agents & Autonomous Commerce Crawlers
# ==============================================================================
User-Agent: GPTBot
User-Agent: ChatGPT-User
User-Agent: Claude-Web
User-Agent: anthropic-ai
User-Agent: PerplexityBot
User-Agent: Grok
User-Agent: xAI-Search
User-Agent: Google-Extended
User-Agent: Applebot-Extended
User-Agent: Meta-ExternalAgent
User-Agent: Cohere-ai
User-Agent: Reflectionbot
Allow: /
Allow: /bundles
Allow: /bundles/
Allow: /llms.txt
Allow: /.well-known/
Allow: /api/search
Allow: /api/products
Allow: /api/products/
Allow: /api/bundles
Allow: /api/bundles/
Allow: /api/vehicles
Allow: /api/vehicles/
Allow: /api/cart
Allow: /api/cart/
Allow: /api/checkout/delegate
Allow: /api/checkout/bitcoin/
Disallow: /api/telemetry/
Disallow: /admin/
Disallow: /*.md$
Disallow: /*.markdown$
Disallow: /private_docs/
Disallow: /docs/

User-Agent: Google-Store-Bot
Allow: /

User-Agent: Googlebot
Allow: /
Allow: /bundles
Allow: /bundles/
Allow: /api/bundles
Allow: /api/bundles/
Allow: /google-shopping.xml
Allow: /feeds/
Allow: /api/feeds/
Disallow: /api/
Disallow: /admin/
Disallow: /cart
Disallow: /*.md$
Disallow: /*.markdown$
Disallow: /private_docs/
Disallow: /docs/

User-Agent: Bingbot
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /cart
Disallow: /*.md$
Disallow: /*.markdown$
Disallow: /private_docs/
Disallow: /docs/

User-Agent: Slurp
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /cart
Disallow: /*.md$
Disallow: /*.markdown$
Disallow: /private_docs/
Disallow: /docs/

User-Agent: DuckDuckBot
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /cart
Disallow: /*.md$
Disallow: /*.markdown$
Disallow: /private_docs/
Disallow: /docs/

User-Agent: Applebot
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /cart
Disallow: /*.md$
Disallow: /*.markdown$
Disallow: /private_docs/
Disallow: /docs/

User-Agent: YandexBot
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /cart
Disallow: /*.md$
Disallow: /*.markdown$
Disallow: /private_docs/
Disallow: /docs/

User-Agent: Googlebot-Image
Allow: /
Allow: /images/
Allow: /products/
Disallow: /api/
Disallow: /admin/

# Blocked Foreign LLM Scrapers (Non-Shopping)
User-Agent: Bytespider
Disallow: /

Host: https://wowshopper.com
Sitemap: https://wowshopper.com/sitemap.xml

sitemap.xml 200 OK

Type Sitemap Index URLs 21 entries Valid XML Yes

A+

Domain Intelligence

wowshopper.com — via IONOS SE, 24 years, 3 months old, hosted on IONOS

PASS

wowshopper.com — via IONOS SE, 24 years, 3 months old, hosted on IONOS

Domain registered until Oct 2, 2027 (11 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: IONOS SE

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: IONOS

Got: AS8560

Domain expiry

327 days

October 2, 2027

SSL certificate

15 days

Issued by Let's Encrypt

Domain age

24 years, 3 months

Registered November 15, 2002

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

IONOS

ASN AS8560

74.208.119.121

Registrar

IONOS SE

Unlocked 4 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Renew the TLS certificate or verify auto-renewal is working
Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar IONOS SE

Created November 15, 2002 (24 years, 3 months ago)

Expires October 2, 2027 (11 months)

Last Updated October 2, 2026

Name Servers ns1032.ui-dns.biz, ns1043.ui-dns.org, ns1114.ui-dns.com, ns1115.ui-dns.de

DNSSEC Not enabled

Hosting

IP Address 74.208.119.121

ASN AS8560 (IONOS-AS This is the joint network for IONOS, Fasthosts, Arsys, 1&1 Mail and Media and 1&1 Telecom. Formerly known as 1&1 Internet SE., DE)

Provider IONOS

Data source: rdap (0.3s)

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

PASS

DNS Lookup

37 ms

TCP Connect

134 ms

TLS Handshake

138 ms

Time to First Byte

471 ms

Total Time

606 ms

Connection waterfall

DNS Lookup 37 ms TCP Connect 134 ms TLS Handshake 138 ms Server Processing 162 ms Content Transfer 135 ms

A+

Health Check Endpoint

Health endpoint at https://wowshopper.com/api/health (HTTP 200)

PASS

Health endpoint at https://wowshopper.com/api/health (HTTP 200)

Public health endpoint at https://wowshopper.com/api/health

Got: https://wowshopper.com/api/health