Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
BReverse DNS0/1 IPs match cert SANREVIEW
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BCrawlabilityno robots.txt, no sitemapREVIEW
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
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.
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
No robots.txt found
This is fine for most sites — a missing robots.txt allows all crawling by default.
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations56 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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
BCDN & DeliveryDocument on Cloudflare; assets also on Google Cloud CDN, Shopify, Fastly, AWS CloudFrontREVIEW
Asset hosts on a CDN
- cdn.shopify.com — Google Cloud CDN · assets: 197
- www.littlepartydress.com.au — Shopify · assets: 59 · Cache Status: HIT
- cdn.rebuyengine.com — Cloudflare · assets: 23 · Cache Status: HIT
- static.klaviyo.com — Fastly · assets: 9 · Cache Status: DYNAMIC
- js.smile.io — AWS CloudFront · assets: 5 · Cache Status: RefreshHit from cloudfront
- static-tracking.klaviyo.com — Fastly · assets: 4 · Cache Status: HIT, HIT
Other asset hosts
- www.googletagmanager.com — assets: 5 · Google
- adsagentclientafd-b7hqhjdrf3fpeqh2.b01.azurefd.net — assets: 2 · below probe threshold
- cached.rebuyengine.com — assets: 2 · below probe threshold
- cdn-static.okendo.io — assets: 2 · below probe threshold
- config.gorgias.chat — assets: 2 · below probe threshold
- connect.facebook.net — assets: 2 · below probe threshold
- content.9gtb.com — assets: 2 · below probe threshold
- ajax.googleapis.com — assets: 1 · below probe threshold
- analytics.ahrefs.com — assets: 1 · below probe threshold
- config.gorgias.help — assets: 1 · below probe threshold
- contactform.herokuapp.com — assets: 1 · below probe threshold
- scripts.clarity.ms — assets: 1 · below probe threshold
- shop.app — assets: 1 · below probe threshold
- swymv3premium-01.azureedge.net — assets: 1 · below probe threshold
- www.clarity.ms — assets: 1 · below probe threshold
BCDN Cache ObservabilityNo CDN cache-status headers in the responseREVIEW
BOperational Status PageNo status page link detectedREVIEW
A+DNS Records1 A records, 2 ms lookupPASS
| A | 23.227.38.32 |
| AAAA | — |
| CNAME | — |
| NS | ns2.netregistry.net, ns3.netregistry.net, ns1.netregistry.net |
| MX | 0 littlepartydress-com-au.mail.protection.outlook.com |
| TXT | v=DMARCl:p=none:sp=none;pct=100:rua=mailtosphani@littlepartydress.com.a wiruf=ma... MS=ms53742487 facebook-domain-verification=9g311np1ikkunna8nrrf1m9996grlc apple-domain-verification=NNlSNjn3mibYamwb klaviyo-site-verification=Hgp2uB google-site-verification=RyyK0VFlf9CoGOF7hhiN3vD5sc_tCIUFxShvC3k2aD4 SPF v=spf1 include:shops.shopify.com include:mailgun.org include:spf.protection.outl... |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 20ms across 3 resolvers (spread 10ms)PASS
A+Redirect Chain0 redirect(s), 26 ms totalPASS
https://littlepartydress.com.au
26 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://littlepartydress.com.au | 403 | 26 ms | HTTP/1.1 | cloudflare |
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencelittlepartydress.com.au — via Melbourne IT, hosted on CloudflarePASS
Unknown
56 days
Issued by Let's Encrypt
Unknown
Not enabled
Protects against DNS spoofing
Cloudflare
ASN AS13335
23.227.38.32
Melbourne IT
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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