https://marie-nicole-girls-outfits.myshopify.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Probed from Santa Clara, United States

429 Too Many Requests

Checks

10 PASS 5 REVIEW 1 FIX

IPv6 Readiness

Action

IPv6 records exist but unreachable

FIX

IPv6 records exist but unreachable

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: 2620:127:f00f:e::

IPv6 connection error

Got: dial tcp6 [2620:127:f00f:e::]:443: connect: network is unreachable

IPv6 Misconfigured

AAAA Records 2620:127:f00f:e:: 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)

DNS Records

1 A records, 18 ms lookup

REVIEW

1 A records, 18 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: 18 ms

Got: 18 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 18 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)

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).

Crawlability

no robots.txt, no sitemap

REVIEW

no robots.txt, no sitemap

No robots.txt found

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

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.

TLS Certificate Expiry & Recommendations

45 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

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

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+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

CNAME does not point at a known takeover-able service

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.

Reverse DNS

1/2 IPs match cert SAN

PASS

1/2 IPs match cert SAN

PTR for 23.227.38.74 matches certificate SAN: shops.myshopify.com

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 11ms across 3 resolvers (spread 5ms)

PASS

Mean 11ms across 3 resolvers (spread 5ms)

Quad9: 8ms

Got: 8ms via 9.9.9.9:53

Cloudflare: 12ms

Got: 12ms via 1.1.1.1:53

Google: 13ms

Got: 13ms via 8.8.8.8:53

A+

Redirect Chain

0 redirect(s), 69 ms total

PASS

0 redirect(s), 69 ms total

https://marie-nicole-girls-outfits.mysho...

69 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://marie-nicole-girls-outfits.mysho...	403	69 ms	HTTP/1.1	cloudflare

A+

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

https://www.marie-nicole-girls-outfits.myshopify.com/

200https://marie-nicole-girls-outfits.myshopify.com/

HTTP → HTTPS

301http://marie-nicole-girls-outfits.myshopify.com/ → https://marie-nicole-girls-outfits.myshopify.com/

Consistent

A+

HTTP Probe Timing

Total 135 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

7 ms

TCP Connect

4 ms

TLS Handshake

14 ms

Time to First Byte

136 ms

Total Time

136 ms

Connection waterfall

DNS Lookup 7 ms TCP Connect 4 ms TLS Handshake 14 ms Server Processing 111 ms Content Transfer 0 ms

CDN & Delivery

Document on Shopify; assets also on AWS CloudFront, Cloudflare, Fastly

PASS

Document on Shopify; assets also on AWS CloudFront, Cloudflare, Fastly

Document is served via Shopify CDN

Got: delegation shops.myshopify.com

CDN cache status: DYNAMIC

Assets on AWS CloudFront: cdn-static.okendo.io (assets: 54), cache Hit from cloudfront

Got: x-amz-cf-id: 4n-7T5ZLDqslucHOIWsBGXq9LF0i4Tu1gSHNZB4uwXHTg65K0necEA==

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

Got: cf-ray: a4d29093bde915ff-SJC

Assets on Fastly: static.klaviyo.com (assets: 16), cache DYNAMIC

Got: delegation klaviyo-onsite.map.fastly.net

Assets on Fastly: static-tracking.klaviyo.com (assets: 5), cache HIT, HIT

Got: delegation klaviyo-app.map.fastly.net

Document served via CDN: Shopify

Provider Shopify Cache Status DYNAMIC Evidence delegation shops.myshopify.com

Asset hosts on a CDN

cdn-static.okendo.io — AWS CloudFront · assets: 54 · Cache Status: Hit from cloudfront
cdn.shopify.com — Cloudflare · assets: 17 · Cache Status: HIT
static.klaviyo.com — Fastly · assets: 16 · Cache Status: DYNAMIC
static-tracking.klaviyo.com — Fastly · assets: 5 · Cache Status: HIT, HIT

Other asset hosts

bat.bing.com — assets: 3 · Microsoft Azure
www.googletagmanager.com — assets: 3 · Google
a.klaviyo.com — assets: 2 · below probe threshold
ecommplugins-scripts.trustpilot.com — assets: 2 · below probe threshold
sdk.loyaltylion.net — assets: 2 · below probe threshold
cdn.intelligems.io — assets: 1 · below probe threshold
ecommplugins-trustboxsettings.trustpilot.com — assets: 1 · below probe threshold
invitejs.trustpilot.com — assets: 1 · below probe threshold
js.squarecdn.com — assets: 1 · below probe threshold
navidium-static-assets.s3.amazonaws.com — assets: 1 · below probe threshold
sapi.negate.io — assets: 1 · below probe threshold
shop.app — assets: 1 · below probe threshold
static.afterpay.com — assets: 1 · below probe threshold
swymv3premium-01.azureedge.net — assets: 1 · below probe threshold
widget.sezzle.com — assets: 1 · below probe threshold

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://marie-nicole-girls-outfits.myshopify.com/healthz (HTTP 200)

PASS

Health endpoint at https://marie-nicole-girls-outfits.myshopify.com/healthz (HTTP 200)

Public health endpoint at https://marie-nicole-girls-outfits.myshopify.com/healthz

Got: https://marie-nicole-girls-outfits.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.