Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations44 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- 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
BCDN & DeliveryNetlifyREVIEW
A+DNS Records2 A records, 24 ms lookupPASS
| A | 18.208.88.157, 98.84.224.111 |
| AAAA | 2600:1f18:16e:df01::259, 2600:1f18:16e:df01::258 |
| CNAME | — |
| NS | pdns1.registrar-servers.com, pdns2.registrar-servers.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 | facebook-domain-verification=gcrjpnd6r0299823s7td3n0b8yiei4 google-site-verification=8y9jzxQsgI0yvA2xzpXAvgXSArh2WlG8j806DSKxyDo google-site-verification=LXhSineS8EmbTl_9dt0fycuoHZuTKcUGHXtvU8GYyCE google-site-verification=QmXLdAexsp8knY7WVmq-PCi-237UuviRvFji1bw-cd4 google-site-verification=bczwxUheqRyCwcCs3XhTxTLdk8FqEFS0XJhFhy0s6lM SPF v=spf1 ip4:69.80.200.244 ip4:69.80.200.225 include:_spf.google.com ~all |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
ARedirect Chain1 redirect(s), 323 ms totalPASS
https://purevolume.com
302 ms · HTTP/1.1
https://www.purevolume.com/
21 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://purevolume.com | 301 | 302 ms | HTTP/1.1 | Netlify |
| 2 | https://www.purevolume.com/ | 200 | 21 ms | HTTP/1.1 | nginx |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (94 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 4 URLsPASS
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
User-agent: *
Allow: /ads.txt
Disallow: /trackback/
Disallow: /comments/
Disallow: /cgi-bin
Disallow: /wp-admin/
Disallow: /?s=*
Disallow: /stats/
Disallow: /events/
Disallow: /search/
Disallow: /21287525/
Disallow: /author
Disallow: /wget/
Disallow: /httpd/
Disallow: /wp-content/uploads/
Crawl-delay: 30
User-agent: Googlebot-Image
Disallow: /
User-agent: Twitterbot
Allow: /wp-content/uploads/
User-agent: facebookexternalhit
Allow: /wp-content/uploads/
User-agent: ia_archiver
Disallow: /
User-agent: PetalBot
Disallow: /
A+Domain Intelligencepurevolume.com — via GoDaddy.com, LLC, 22 years, 9 months oldPASS
228 days
January 30, 2027
44 days
Issued by Let's Encrypt
22 years, 9 months
Registered November 17, 2003
Not enabled
Protects against DNS spoofing
Unknown
2600:1f18:16e:df01::258
GoDaddy.com, LLC
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