Skip to content
https://stocktostove.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
2
REVIEW
8
PASS
7
INFO
0
Probed from New York, United Stated
200 OK
Checks
17
7 PASS 8 REVIEW 2 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2606:4700:3035::ac43:87bf, 2606:4700:3036::6815:72f
Info::
IPv6 connection error
Got: dial tcp6 [2606:4700:3035::ac43:87bf]:443: connect: no route to host
IPv6 Misconfigured
AAAA Records 2606:4700:3035::ac43:87bf, 2606:4700:3036::6815:72f Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 200 Expected: 301 redirect to HTTPS

www / non-www

200https://www.stocktostove.com/
200https://stocktostove.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

200http://stocktostove.com/

HTTP version does not redirect to HTTPS

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
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)
Info::
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
Info::
PTR lookup failed for 172.67.135.191: lookup 172.67.135.191: 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.
Info::
PTR lookup failed for 104.21.7.47: lookup 104.21.7.47: 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.
Info::
PTR lookup failed for 2606:4700:3035::ac43:87bf: lookup 2606:4700:3035::ac43:87bf: 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.
Info::
PTR lookup failed for 2606:4700:3036::6815:72f: lookup 2606:4700:3036::6815:72f: 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
Multi-Resolver DNS Speed
Mean 65ms across 3 resolvers (spread 163ms)
REVIEW
Mean 65ms across 3 resolvers (spread 163ms)
Info::
Cloudflare: 2ms
Got: 2ms via 1.1.1.1:53
Info::
Google: 29ms
Got: 29ms via 8.8.8.8:53
Info::
Quad9: 165ms
Got: 165ms via 9.9.9.9:53
B
TLS Certificate Expiry & Recommendations
80 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

80
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
B
CDN & Delivery
Cloudflare (REVALIDATED)
REVIEW
Cloudflare (REVALIDATED)
Info::
Document is served via Cloudflare CDN (edge: EWR)
Got: cf-ray: a39741d0ff0ff98d-EWR
Info::
CDN cache status: REVALIDATED
Document served via CDN: Cloudflare
Provider Cloudflare Cache Status REVALIDATED Evidence cf-ray: a39741d0ff0ff98d-EWR
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
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
Info::
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+
DNS Records
2 A records, 36 ms lookup
PASS
2 A records, 36 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.67.135.191, 104.21.7.47
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3035::ac43:87bf, 2606:4700:3036::6815:72f
Info::
2 nameserver(s) configured
Got: chuck.ns.cloudflare.com, eloise.ns.cloudflare.com
Info::
3 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 36 ms
Got: 36 ms
A172.67.135.191, 104.21.7.47
AAAA2606:4700:3035::ac43:87bf, 2606:4700:3036::6815:72f
CNAME—
NSchuck.ns.cloudflare.com, eloise.ns.cloudflare.com
MX
6 route2.mx.cloudflare.net
9 route1.mx.cloudflare.net
100 route3.mx.cloudflare.net
TXT
google-site-verification=qStQXYEgW2iHFbGULUZx5i7FDQAlj5c_irJpocXF1Cs
SPF v=spf1 include:_spf.mx.cloudflare.net ~all
CAALookup not available with standard resolver
Resolved in 36 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://stocktostove.com

https://stocktostove.com

220 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://stocktostove.com200220 msHTTP/1.1cloudflare
A+
Crawlability
robots.txt present, sitemap with 1 URLs
PASS
robots.txt present, sitemap with 1 URLs
Info::
robots.txt is present
Got: 2199 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1 entries
Info::
Sitemap index with 1 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2199 B Sitemaps referenced 1 User-agents *, Bytespider, CloudflareBrowserRenderingCrawler, Google-Extended, meta-externalagent, Amazonbot, Applebot-Extended, CCBot, ClaudeBot, GPTBot 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: /

User-agent: Amazonbot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: CloudflareBrowserRenderingCrawler
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: meta-externalagent
Disallow: /

# END Cloudflare Managed Content

User-agent: *
Allow: /
Disallow: /admin
Disallow: /api
Disallow: /results
Disallow: /es/results
Disallow: /fr/results
Disallow: /de/results
Disallow: /pt/results
Disallow: /it/results
Disallow: /hi/results
Disallow: /gu/results
Disallow: /ta/results
Disallow: /ar/results
Disallow: /zh/results
Disallow: /ja/results

Sitemap: https://stocktostove.com/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 1 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
stocktostove.com — via Spaceship, Inc., 9 days old
PASS
stocktostove.com — via Spaceship, Inc., 9 days old
Info::
Domain registered until Sep 1, 2027 (11 months remaining)
Info::
Domain is only 9 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 Sep 1, 2026
Info::
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.
Info::
Registrar: Spaceship, Inc.
Warning::
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

354 days

September 1, 2027

SSL certificate

80 days

Issued by Google Trust Services

Domain age

9 days

Registered September 1, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3035::ac43:87bf

Registrar

Spaceship, 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 Spaceship, Inc.
Created September 1, 2026 (9 days ago)
Expires September 1, 2027 (11 months)
Last Updated September 2, 2026
Name Servers chuck.ns.cloudflare.com, eloise.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:3035::ac43:87bf
Data source: rdap (0.1s)

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 108 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
19 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
2 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
11 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
107 ms
Total Time Total request time from DNS lookup through full response.
108 ms

Connection waterfall

DNS Lookup 19 ms TCP Connect 2 ms TLS Handshake 11 ms Server Processing 75 ms Content Transfer 2 ms
A+
CDN Cache Observability
Cache state: REVALIDATED
PASS
Cache state: REVALIDATED
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=REVALIDATED
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback