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 Sao Paulo, Brazil

403 Forbidden

Checks

6 PASS 11 REVIEW

DNS Records

1 A records, 256 ms lookup

REVIEW

1 A records, 256 ms lookup

Resolves to 1 IPv4 address(es)

Got: 23.227.38.32

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

2 nameserver(s) configured

Got: ns49.domaincontrol.com, ns50.domaincontrol.com

5 mail exchanger(s) configured

No SPF record found in TXT records

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

DNS resolution is slow (256 ms)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Got: 256 ms

A	23.227.38.32
AAAA	—
CNAME	—
NS	ns49.domaincontrol.com, ns50.domaincontrol.com
MX	1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com
TXT	—
CAA	Lookup not available with standard resolver

Resolved in 256 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

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)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

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

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.

Reverse DNS

0/1 IPs match cert SAN

REVIEW

0/1 IPs match cert SAN

PTR for 23.227.38.32 does not match any cert SAN: myshopify.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.

Multi-Resolver DNS Speed

Action

Mean 110ms across 3 resolvers (spread 211ms)

REVIEW

Mean 110ms across 3 resolvers (spread 211ms)

Cloudflare: 2ms

Got: 2ms via 1.1.1.1:53

Google: 116ms

Got: 116ms via 8.8.8.8:53

Quad9: 213ms

Got: 213ms via 9.9.9.9:53

High latency spread between resolvers: 211ms (min 2ms / max 213ms)

Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.

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

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

70 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

CDN & Delivery

Document and assets on Cloudflare

REVIEW

Document and assets on Cloudflare

Document is served via Cloudflare CDN (edge: GRU)

Got: cf-ray: a4c90a9f9d4c8bf6-GRU

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

Got: cf-ray: a4c90c0a9e271a93-GRU

Document served via CDN: Cloudflare

Provider Cloudflare Evidence cf-ray: a4c90a9f9d4c8bf6-GRU

Asset hosts on a CDN

cdn.shopify.com — Cloudflare · assets: 6 · Cache Status: HIT

Other asset hosts

connect.facebook.net — assets: 2 · below probe threshold
cdn.hextom.com — assets: 1 · below probe threshold
loox.io — assets: 1 · below probe threshold
shop.app — assets: 1 · below probe threshold

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.

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

No CNAME record present

A+

Redirect Chain

0 redirect(s), 252 ms total

PASS

0 redirect(s), 252 ms total

https://smoochiebaby.com

252 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://smoochiebaby.com	403	252 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

429https://www.smoochiebaby.com/

200https://smoochiebaby.com/

HTTP → HTTPS

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

Consistent

Domain Intelligence

smoochiebaby.com — via GoDaddy.com, LLC, 22 years, 2 months old, hosted on Cloudflare

PASS

smoochiebaby.com — via GoDaddy.com, LLC, 22 years, 2 months old, hosted on Cloudflare

Domain expires in 35 days

Consider enabling auto-renewal to prevent accidental expiration.

Got: Expires Nov 23, 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: GoDaddy.com, LLC

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

Got: AS13335

Domain expiry

35 days

November 23, 2026

SSL certificate

70 days

Issued by Let's Encrypt

Domain age

22 years, 2 months

Registered November 23, 2004

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

23.227.38.32

Registrar

GoDaddy.com, LLC

Unlocked 2 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Renew the domain or enable auto-renewal to prevent accidental expiry
Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar GoDaddy.com, LLC

Created November 23, 2004 (22 years, 2 months ago)

Expires November 23, 2026 (1 months)

Last Updated November 23, 2025

Name Servers ns49.domaincontrol.com, ns50.domaincontrol.com

DNSSEC Not enabled

Hosting

IP Address 23.227.38.32

ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)

Provider Cloudflare

Data source: rdap (0.8s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

PASS

DNS Lookup

362 ms

TCP Connect

2 ms

TLS Handshake

14 ms

Time to First Byte

390 ms

Total Time

391 ms

Connection waterfall

DNS Lookup 362 ms TCP Connect 2 ms TLS Handshake 14 ms Server Processing 12 ms Content Transfer 1 ms

A+

Health Check Endpoint

Health endpoint at https://smoochiebaby.com/healthz (HTTP 200)

PASS

Health endpoint at https://smoochiebaby.com/healthz (HTTP 200)

Public health endpoint at https://smoochiebaby.com/healthz

Got: https://smoochiebaby.com/healthz

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