Infrastructure - https://m4center.store 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.96.147: lookup 104.21.96.147: 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.182.213: lookup 172.67.182.213: 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::6815:6093: lookup 2606:4700:3035::6815:6093: 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:3037::ac43:b6d5: lookup 2606:4700:3037::ac43:b6d5: 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

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.m4center.store/

200https://m4center.store/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://m4center.store/ → https://m4center.store/

Consistent

B

TLS Certificate Expiry & Recommendations

89 days until leaf cert expires — 5 issues to address

REVIEW

Certificate validity

89

days left

0d 30d 60d 90d+

Recommended actions

Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
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.

A+

DNS Records

2 A records, 44 ms lookup

PASS

2 A records, 44 ms lookup

Resolves to 2 IPv4 address(es)

Got: 104.21.96.147, 172.67.182.213

Has 2 IPv6 (AAAA) record(s)

Got: 2606:4700:3035::6815:6093, 2606:4700:3037::ac43:b6d5

2 nameserver(s) configured

Got: watson.ns.cloudflare.com, lana.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: 44 ms

Got: 44 ms

A	104.21.96.147, 172.67.182.213
AAAA	2606:4700:3035::6815:6093, 2606:4700:3037::ac43:b6d5
CNAME	—
NS	watson.ns.cloudflare.com, lana.ns.cloudflare.com
MX	—
TXT	—
CAA	Lookup not available with standard resolver

Resolved in 44 ms

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)

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A+

Multi-Resolver DNS Speed

Mean 29ms across 3 resolvers (spread 13ms)

PASS

Mean 29ms across 3 resolvers (spread 13ms)

Cloudflare: 23ms

Got: 23ms via 1.1.1.1:53

Google: 28ms

Got: 28ms via 8.8.8.8:53

Quad9: 36ms

Got: 36ms via 9.9.9.9:53

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://m4center.store

https://m4center.store

178 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://m4center.store	200	178 ms	HTTP/1.1	cloudflare

A+

IPv6 Readiness

IPv6 reachable (17 ms)

PASS

IPv6 reachable (17 ms)

IPv6 is configured and reachable at 2606:4700:3035::6815:6093, 2606:4700:3037::ac43:b6d5

Got: 17 ms connect

IPv6 Ready

AAAA Records 2606:4700:3035::6815:6093, 2606:4700:3037::ac43:b6d5 Connection Reachable (17 ms)

A+

Crawlability

robots.txt present, sitemap with 28 URLs

PASS

robots.txt present, sitemap with 28 URLs

robots.txt is present

Got: 3283 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 28 entries

robots.txt does not reference a sitemap

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 3283 B Sitemaps referenced 0 User-agents WARDBot, Bytespider, Google-Extended, omgili, MistralAI-Training, BorderxBot, Claude-User, ChatGPT-User, Applebot-Extended, Diffbot, atlassian-bot, FirecrawlAgent, Google-NotebookLM, MistralAI-User, Instapaper, GoogleOther, Baiduspider, AwarioSmartBot, FishBot, GPTBot, cohere-ai, ICC-Crawler, Amzn-User, *, CCBot, AwarioRssBot, Perplexity-User, Google-Agent, Kimi-User, ChathiveCrawler, Amazonbot, Claude-Web, PetalBot, QualifiedBot, magpie-crawler, FireCrawl, meta-externalfetcher, Retool, meta-externalagent, Google-CloudVertexBot, NavuBot, SemrushBot-SWA, KimiBot, CitibotSiteCrawler, Google-GeminiNotebook, ClaudeBot, anthropic-ai, Cotoyogi Blocking No — crawling allowed

# As a condition of accessing this website, you agree to abide by the following
# content signals:

# (a)  If a Content-Signal = yes, you may collect content for the corresponding
#      use.
# (b)  If a Content-Signal = no, you may not collect content for the
#      corresponding use.
# (c)  If the website operator does not include a Content-Signal for a
#      corresponding use, the website operator neither grants nor restricts
#      permission via Content-Signal with respect to the corresponding use.

# The content signals and their meanings are:

# search:   building a search index and providing search results (e.g., returning
#           hyperlinks and short excerpts from your website's contents). Search does not
#           include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
#           augmented generation, grounding, or other real-time taking of content for
#           generative AI search answers).
# ai-train: training or fine-tuning AI models.
# use:      how AI systems may consume the content (immediate, reference, or full).

# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.

# BEGIN Cloudflare Managed content


User-agent: *
Content-Signal: search=yes,ai-train=no,use=reference
Allow: /

# Training crawlers
User-agent: Amazonbot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Diffbot
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: omgili
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: Claude-Web
Disallow: /

User-agent: cohere-ai
Disallow: /

User-agent: MistralAI-Training
Disallow: /

User-agent: meta-externalagent
Disallow: /

User-agent: GoogleOther
Disallow: /

User-agent: Baiduspider
Disallow: /

User-agent: PetalBot
Disallow: /

User-agent: AwarioSmartBot
User-agent: AwarioRssBot
Disallow: /

User-agent: Google-CloudVertexBot
Disallow: /

User-agent: QualifiedBot
Disallow: /

User-agent: Cotoyogi
Disallow: /

User-agent: ICC-Crawler
Disallow: /

User-agent: atlassian-bot
Disallow: /

User-agent: FishBot
Disallow: /

User-agent: BorderxBot
Disallow: /

User-agent: NavuBot
Disallow: /

User-agent: SemrushBot-SWA
Disallow: /

User-agent: WARDBot
Disallow: /

User-agent: magpie-crawler
Disallow: /

User-agent: KimiBot
Disallow: /

User-agent: CitibotSiteCrawler
Disallow: /

# AI Agents
User-agent: Perplexity-User
Disallow: /

User-agent: FireCrawl
Disallow: /

User-agent: FirecrawlAgent
Disallow: /

User-agent: Claude-User
Disallow: /

User-agent: ChatGPT-User
Disallow: /

User-agent: Google-Agent
Disallow: /

User-agent: Google-GeminiNotebook
User-agent: Google-NotebookLM
Disallow: /

User-agent: MistralAI-User
Disallow: /

User-agent: Kimi-User
Disallow: /

User-agent: Amzn-User
Disallow: /

User-agent: meta-externalfetcher
Disallow: /

User-agent: Retool
Disallow: /

User-agent: Instapaper
Disallow: /

User-agent: ChathiveCrawler
Disallow: /

# END Cloudflare Managed Content

User-agent: *
Disallow:

sitemap.xml 200 OK

Type URL Set URLs 28 entries Valid XML Yes

Sample URLs:

A+

Domain Intelligence

m4center.store — via NameCheap, Inc., 0 days old

PASS

m4center.store — via NameCheap, Inc., 0 days old

Domain registered until Nov 6, 2027 (1 years remaining)

Domain is only 0 days old

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Got: Registered Nov 6, 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.

Domain expiry

363 days

November 6, 2027

SSL certificate

89 days

Issued by Let's Encrypt

Domain age

0 days

Registered November 6, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3037::ac43:b6d5

Registrar

NameCheap, 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
Newly registered domain — build backlinks and content to establish SEO trust
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar NameCheap, Inc.

Created November 6, 2026 (0 days ago)

Expires November 6, 2027 (1 years)

Last Updated November 6, 2026

Name Servers lana.ns.cloudflare.com, watson.ns.cloudflare.com

DNSSEC Not enabled

Hosting

IP Address 2606:4700:3037::ac43:b6d5

Data source: rdap (0.5s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

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

PASS

DNS Lookup

37 ms

TCP Connect

17 ms

TLS Handshake

29 ms

Time to First Byte

269 ms

Total Time

270 ms

Connection waterfall

DNS Lookup 37 ms TCP Connect 17 ms TLS Handshake 29 ms Server Processing 186 ms Content Transfer 0 ms

A

CDN & Delivery

Cloudflare (DYNAMIC)

PASS

Cloudflare (DYNAMIC)

Document is served via Cloudflare CDN (edge: CDG)

Got: cf-ray: a56668cbcef27910-CDG

CDN cache status: DYNAMIC

Document served via CDN: Cloudflare

Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a56668cbcef27910-CDG

A+

CDN Cache Observability

Cache state: DYNAMIC

PASS

Cache state: DYNAMIC

CDN cache state observable via 1 header(s)

Got: cf-cache-status=DYNAMIC

A+

Health Check Endpoint

Health endpoint at https://m4center.store/health (HTTP 200)

PASS

Health endpoint at https://m4center.store/health (HTTP 200)

Public health endpoint at https://m4center.store/health

Got: https://m4center.store/health