Skip to content
https://oak-clothing-co.myshopify.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
0
REVIEW
7
PASS
9
INFO
1
Probed from Madrid, Spain
403 Forbidden
Checks
17
9 PASS 7 REVIEW
B
DNS Records
1 A records, 29 ms lookup
REVIEW
1 A records, 29 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.227.38.74
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2620:127:f00f:e::
Warning::
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
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 29 ms
Got: 29 ms
A23.227.38.74
AAAA2620:127:f00f:e::
CNAMEshops.myshopify.com
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 29 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)
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
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
TLS Certificate Expiry & Recommendations
45 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

45
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
Document on Shopify; assets also on Cloudflare
REVIEW
Document on Shopify; assets also on Cloudflare
Info::
Document is served via Shopify CDN
Got: delegation shops.myshopify.com
Info::
Assets on Cloudflare: cdn-uav.vitals.app (assets: 8), cache DYNAMIC
Got: cf-ray: a4d29ad32a42d08f-CDG
Info::
Assets on Cloudflare: cdn.shopify.com (assets: 3), cache HIT
Got: cf-ray: a4d29ad2eeded56c-CDG
Document served via CDN: Shopify
Provider Shopify Evidence delegation shops.myshopify.com

Asset hosts on a CDN

  • cdn-uav.vitals.app — Cloudflare · assets: 8 · Cache Status: DYNAMIC
  • cdn.shopify.com — Cloudflare · assets: 3 · Cache Status: HIT

Other asset hosts

  • cdn.one.store — assets: 2 · below probe threshold
  • chimpstatic.com — assets: 2 · below probe threshold
  • connect.facebook.net — assets: 2 · below probe threshold
  • form-assets.mailchimp.com — assets: 2 · below probe threshold
  • cdn-sf.vitals.app — assets: 1 · below probe threshold
  • shop.app — 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
Info::
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
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.
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
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
Info::
CAA issue tag present — authorized CA(s): digicert.com, globalsign.com, letsencrypt.org, pki.goog, ssl.com
Info::
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
Reverse DNS
1/2 IPs match cert SAN
PASS
1/2 IPs match cert SAN
Info::
PTR for 23.227.38.74 matches certificate SAN: shops.myshopify.com
Info::
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.
A+
Multi-Resolver DNS Speed
Mean 18ms across 3 resolvers (spread 23ms)
PASS
Mean 18ms across 3 resolvers (spread 23ms)
Info::
Quad9: 6ms
Got: 6ms via 9.9.9.9:53
Info::
Cloudflare: 20ms
Got: 20ms via 1.1.1.1:53
Info::
Google: 29ms
Got: 29ms via 8.8.8.8:53
A+
Redirect Chain
0 redirect(s), 78 ms total
PASS
0 redirect(s), 78 ms total

https://oak-clothing-co.myshopify.com

78 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://oak-clothing-co.myshopify.com40378 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
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+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

https://www.oak-clothing-co.myshopify.com/
200https://oak-clothing-co.myshopify.com/

HTTP → HTTPS

301http://oak-clothing-co.myshopify.com/ → https://oak-clothing-co.myshopify.com/

Consistent

A+
HTTP Probe Timing
Total 101 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
31 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
25 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
101 ms
Total Time Total request time from DNS lookup through full response.
101 ms

Connection waterfall

DNS Lookup 31 ms TCP Connect 17 ms TLS Handshake 25 ms Server Processing 28 ms Content Transfer 1 ms
A+
Health Check Endpoint
Health endpoint at https://oak-clothing-co.myshopify.com/healthz (HTTP 200)
PASS
Health endpoint at https://oak-clothing-co.myshopify.com/healthz (HTTP 200)
Info::
Public health endpoint at https://oak-clothing-co.myshopify.com/healthz
Got: https://oak-clothing-co.myshopify.com/healthz
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback