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 Madrid, Spain

200 OK

Checks

9 PASS 8 REVIEW

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/2 IPs match cert SAN

REVIEW

0/2 IPs match cert SAN

PTR for 23.227.38.69 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.

PTR lookup failed for 2620:127:f00f:9::: lookup 2620:127:f00f:9::: 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.

Multi-Resolver DNS Speed

Action

Mean 113ms across 3 resolvers (spread 255ms)

REVIEW

Mean 113ms across 3 resolvers (spread 255ms)

Google: 20ms

Got: 20ms via 8.8.8.8:53

Quad9: 44ms

Got: 44ms via 9.9.9.9:53

Cloudflare: 275ms

Got: 275ms via 1.1.1.1:53

High latency spread between resolvers: 255ms (min 20ms / max 275ms)

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.

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

58 days until leaf cert expires — 5 issues to address

REVIEW

Certificate validity

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

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.

Health Check Endpoint

No conventional health endpoint found

REVIEW

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: 429, /healthz: 429, /ping: 429, /status: 429.

DNS Records

1 A records, 31 ms lookup

PASS

1 A records, 31 ms lookup

Resolves to 1 IPv4 address(es)

Got: 23.227.38.69

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

4 nameserver(s) configured

Got: ns-cloud-d1.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d4.googledomains.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 time: 31 ms

Got: 31 ms

A	23.227.38.69
AAAA	2620:127:f00f:9::
CNAME	—
NS	ns-cloud-d1.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d4.googledomains.com
MX	1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 alt4.aspmx.l.google.com 10 alt3.aspmx.l.google.com
TXT	—
CAA	Lookup not available with standard resolver

Resolved in 31 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)

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A+

Redirect Chain

0 redirect(s), 80 ms total

PASS

0 redirect(s), 80 ms total

https://camilynbeth.com

80 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://camilynbeth.com	429	80 ms	HTTP/1.1	cloudflare

A+

IPv6 Readiness

IPv6 reachable (17 ms)

PASS

IPv6 reachable (17 ms)

IPv6 is configured and reachable at 2620:127:f00f:9::

Got: 17 ms connect

IPv6 Ready

AAAA Records 2620:127:f00f:9:: Connection Reachable (17 ms)

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.camilynbeth.com/

200https://camilynbeth.com/

HTTP → HTTPS

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

Consistent

A+

Domain Intelligence

camilynbeth.com — via Tucows Domains Inc., 14 years, 8 months old

PASS

camilynbeth.com — via Tucows Domains Inc., 14 years, 8 months old

Domain registered until Apr 20, 2027 (5 months remaining)

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: Tucows Domains 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

163 days

April 20, 2027

SSL certificate

58 days

Issued by Let's Encrypt

Domain age

14 years, 8 months

Registered April 20, 2012

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2620:127:f00f:9::

Registrar

Tucows Domains Inc.

Unlocked 4 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
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar Tucows Domains Inc.

Created April 20, 2012 (14 years, 8 months ago)

Expires April 20, 2027 (5 months)

Last Updated April 7, 2026

Name Servers ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com

DNSSEC Not enabled

Hosting

IP Address 2620:127:f00f:9::

Data source: rdap (0.2s)

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

PASS

DNS Lookup

35 ms

TCP Connect

17 ms

TLS Handshake

27 ms

Time to First Byte

327 ms

Total Time

346 ms

Connection waterfall

DNS Lookup 35 ms TCP Connect 17 ms TLS Handshake 27 ms Server Processing 248 ms Content Transfer 19 ms

CDN & Delivery

Document on Cloudflare; assets also on AWS CloudFront, Bunny CDN, Akamai

PASS

Document on Cloudflare; assets also on AWS CloudFront, Bunny CDN, Akamai

Document is served via Cloudflare CDN (edge: CDG)

Got: cf-ray: a51c44daf83ad3a3-CDG

CDN cache status: DYNAMIC

Assets on AWS CloudFront: assets.gemcommerce.com (assets: 23), cache Hit from cloudfront

Got: delegation d3obzj1xdst97v.cloudfront.net

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

Got: cf-ray: a51c483ce92d250f-CDG

Assets on Cloudflare: fonts.cdnfonts.com (assets: 6), cache HIT

Got: cf-ray: a51c483d1af3e84d-CDG

Assets on Bunny CDN: gdprcdn.b-cdn.net (assets: 3)

Got: delegation gdprcdn.b-cdn.net

Assets on Akamai: staticw2.yotpo.com (assets: 3)

Got: delegation dsa.staticw2.yotpo.com-v1.edgekey.net

Document served via CDN: Cloudflare

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

Asset hosts on a CDN

assets.gemcommerce.com — AWS CloudFront · assets: 23 · Cache Status: Hit from cloudfront
cdn.shopify.com — Cloudflare · assets: 16 · Cache Status: HIT
fonts.cdnfonts.com — Cloudflare · assets: 6 · Cache Status: HIT
gdprcdn.b-cdn.net — Bunny CDN · assets: 3
staticw2.yotpo.com — Akamai · assets: 3

Other asset hosts

static.shareasale.com — assets: 2 · below probe threshold
cdn-accessibility.avada.io — assets: 1 · below probe threshold
cdn-widgetsrepository.yotpo.com — assets: 1 · below probe threshold
cdn.nfcube.com — assets: 1 · below probe threshold
d23dclunsivw3h.cloudfront.net — assets: 1 · below probe threshold
shop.app — 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

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