Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BRedirect Chain2 redirect(s), 92 ms totalREVIEW
https://avast.com
8 ms · HTTP/1.1
https://www.avast.com/
54 ms · HTTP/1.1
https://www.avast.com/es-es/index
30 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://avast.com | 301 | 8 ms | HTTP/1.1 | Google Frontend |
| 2 | https://www.avast.com/ | 302 | 54 ms | HTTP/1.1 | AkamaiGHost |
| 3 | https://www.avast.com/es-es/index | 200 | 30 ms | HTTP/1.1 | Apache |
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
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Preferred variant: non-www
HTTP → HTTPS
HTTP version does not redirect to HTTPS
BTLS Certificate Expiry & Recommendations189 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
A+DNS Records1 A records, 29 ms lookupPASS
| A | 23.46.85.125 |
| AAAA | 2a02:26f0:e0:486::21c7, 2a02:26f0:e0:48f::21c7 |
| CNAME | — |
| NS | a26-67.akam.net, a1-182.akam.net, a20-66.akam.net, a13-65.akam.net, a11-66.akam.net, a6-67.akam.net |
| MX | 0 avast-com.mail.protection.outlook.com |
| TXT | segment-site-verification=intxU1LpjrdINW7QHilYM6C9blznrTdI site24x7-signals-domain-verification=d265eba98d152d1c9dafc5b3f5044af8 google-site-verification=iGnE-HdPoFw1rbSBbllQkT1qrXCwnQfOE1qoe50U9QY google-site-verification=0uAqsuocfiKUuALLUDkgZUjTqojKVv14OO-K15mdmuQ MS=ms87582564 SPF v=spf1 redirect=spfc.avast.com _n3mjdpzgvu3opnmknj83rg5ji782y4w google-site-verification=9KZgt0QBAQTOnPP6NKOGigeO-vW176OMT9yjzS7fZD8 apple-domain-verification=1kYfASdchMq7OLKO google-site-verification=k82twljI92zx21IOUUAFZRhI1H9SYuCQ0Sl-yvWhgkk security-notifications=soc@avast.com knowbe4-site-verification=482fcbc151a32d4f6ba2feaebc35407e google-site-verification=8_D4sFKVTwzXbD0Cn5IKiko_fdjkwfkE9ugaAp_DE0M google-site-verification=tHW5WI8bNL1PvDNkvFl7Mm74YmLIzf3Hr90j7mGOVBQ |
| 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
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.
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 9 URLsPASS
User-agent: *
Disallow:
Disallow: /search-results*
Sitemap: https://www.avast.com/sitemap_index.xml
User-agent: PerplexityBot
Disallow: /*&rut=
User-agent: OAI-SearchBot
Allow: /
User-agent: ChatGPT-User
Allow: /
User-agent: GPTBot
Allow: /
User-agent: Perplexity-User
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: Claude-User
Allow: /
User-agent: ClaudeBot
Allow: /
- https://www.avast.com/sitemap_web_1.xml....
- https://www.avast.com/sitemap_web_2.xml....
- https://www.avast.com/sitemap_web_3.xml....
- https://www.avast.com/sitemap_web_4.xml....
- https://www.avast.com/sitemap_web_5.xml....
- https://www.avast.com/sitemap_web_6.xml....
- https://www.avast.com/sitemap_web_7.xml....
- https://www.avast.com/sitemap_web_extras...
- https://www.avast.com/sitemap_web_index....
A+Domain Intelligenceavast.com — via MarkMonitor Inc., 28 years, 11 months oldPASS
1530 days
September 20, 2030
189 days
Issued by Sectigo Limited
28 years, 11 months
Registered October 6, 1997
Not enabled
Protects against DNS spoofing
Unknown
2a02:26f0:e0:48f::21c7
MarkMonitor Inc.
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