Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction2 redirect(s), 2051 ms totalFIX
https://quantcast.com
609 ms · HTTP/1.1
https://www.quantcast.com/
645 ms · HTTP/1.1
https://www.quantcast.com/home
797 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://quantcast.com | 301 | 609 ms | HTTP/1.1 | |
| 2 | https://www.quantcast.com/ | 302 | 645 ms | HTTP/1.1 | istio-envoy |
| 3 | https://www.quantcast.com/home | 200 | 797 ms | HTTP/1.1 | istio-envoy |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
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
BTLS Certificate Expiry & Recommendations65 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
ADNS Records3 A records, 326 ms lookupPASS
| A | 35.155.244.125, 34.209.86.229, 44.240.140.166 |
| AAAA | — |
| CNAME | — |
| NS | ns-1410.awsdns-48.org, ns-1936.awsdns-50.co.uk, ns-33.awsdns-04.com, ns-538.awsdns-03.net |
| 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 | BPL=1841143 MS=ms56396602 adobe-idp-site-verification=d6e7d54447b1d51a3401a373d7ff675ad5c3f0f88085f426edc6... atlassian-domain-verification=TNEt1rCyWHsplrUUz+uiu1yurXFN15SrKggdskmlABeclN4WFL... atlassian-domain-verification=XA8f7T4mp7E17TLV8WuYUZx63z0McRcc022Xk2GaYPkKI1eLzm... atlassian-sending-domain-verification=18af88e9-b0e4-4f86-a2ff-a69def878282 cursor-domain-verification-mc5sbk=UX5uGQGn95QgC9RPqLDWXEbZW docusign=9db9d3dd-9ac0-4c84-a1ed-b42001f378c3 figma-domain-verification=4fc702bb76e41b73822c9341f57c4f590d1a24ef1a1092870436da... google-site-verification=kNP-X1aVptScfikrOYRfzIG0dNjwipm2Gzg_pB8GNFE jamf-site-verification=LVPRnL7n-KrjXIavvBkWXw phxkxg37cgv2j677tsxm05g1bbmqfdd9 salesforce-domain-verification=00D700000008lCS=1TBU100000009Xx slack-domain-verification=eXlmle0DYCdNPJbgH8jwPBBb7AnZHXOsqQX4dxFY SPF v=spf1 include:_spf.google.com include:afb5a32b-spf.mta.getcheckrecipient.com in... |
| 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.
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
A+Crawlabilityrobots.txt present, sitemap with 505 URLsPASS
# https://www.robotstxt.org/robotstxt.html
# Do not modify this file manually, it must be automatically generated by running 'npm run generate'
# If you need to add more pages to disallow, set the 'ignoreOnSitemap' on Builder for that page to on
User-agent: *
Disallow: /edit-symbols
Disallow: /adchoices
Sitemap: https://www.quantcast.com/sitemap.xml
- https://www.quantcast.com/performance-marketing-masterclass-virgin-money-ai-advantage
- https://www.quantcast.com/TheUnfilteredTableDinner
- https://www.quantcast.com/resources/blog/Your-Autonomous-AI-and-Performance-Marketing-Questions-Answered
- https://www.quantcast.com/Quantcast-challenge
- https://www.quantcast.com/resources/pr/Quantcast-appoints-Rebecca-Rosborough-as-chief-marketing-officer
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
ADomain Intelligencequantcast.com — via MarkMonitor Inc., 21 years, 1 months old, hosted on AWSPASS
5 days
June 18, 2026
65 days
Issued by Let's Encrypt
21 years, 1 months
Registered June 18, 2005
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
34.209.86.229
MarkMonitor Inc.
Expiry timeline
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
Consider enabling auto-renewal to prevent accidental expiration.
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.
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