Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.CCrawlabilityActionrobots.txt present, sitemap with 4 URLsREVIEW
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.
Learn more ▾ ▴
Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.
Source: Google Search Central
# Deny all robots that we do not specifically want to allow
User-agent: *
Disallow: /
# Allow these robots only
User-agent: slurp
Allow: /
User-agent: bingbot
Allow: /
User-Agent: Googlebot
Allow: /
User-agent: Googlebot-image
Allow: /
User-agent: MSNBot-media
Allow: /
User-agent: MSNBot
Allow: /
User-agent: Netcraft
Allow: /
User-agent: Googlebot-Mobile
Allow: /
User-agent: AdsBot-Google
Allow: /
User-agent: Googlebot-Video
Allow: /
User-agent: Googlebot-News
Allow: /
User-agent: Mediapartners-Google
Allow: /
User-agent: AdsBots-Google-Mobile
Allow: /
User-agent: Rogerbot
Allow: /
User-agent: PowerMapper
Allow: /
Disallow: /feed/
Disallow: /trackback/
Disallow: /wp-admin/
Disallow: /wp-content/
Disallow: /wp-includes/
Disallow: /xmlrpc.php
Disallow: /wp-
Allow: /wp-content/uploads/
Sitemap: https://www.zimbra.com/sitemap_index.xml
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations63 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
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
ADNS Records1 A records, 205 ms lookupPASS
| A | 23.185.0.2 |
| AAAA | 2620:12a:8000::2, 2620:12a:8001::2 |
| CNAME | — |
| NS | dns1.p05.nsone.net, dns2.p05.nsone.net, dns3.p05.nsone.net, dns4.p05.nsone.net |
| MX | 0 mail.zimbra.com 10 mta03.zcom.email-ash1.synacor.com 10 mta04.zcom.email-ash1.synacor.com |
| TXT | SPF v=spf1 ptr mx ip4:52.7.157.95 ip4:52.70.125.224 ip4:52.204.246.185 ip4:52.205.85... cisco-ci-domain-verification=681f562fa07c58c993c8bfde487542cb70b5b5eef7753e423d2... |
| 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.
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
ARedirect Chain1 redirect(s), 22 ms totalPASS
https://zimbra.com
10 ms · HTTP/1.1
https://www.zimbra.com/
11 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://zimbra.com | 301 | 10 ms | HTTP/1.1 | nginx |
| 2 | https://www.zimbra.com/ | 200 | 11 ms | HTTP/1.1 | nginx |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
ADomain Intelligencezimbra.com — via CSC Corporate Domains, Inc., 25 years, 3 months oldPASS
EXPIRED
June 1, 2026
63 days
Issued by Let's Encrypt
25 years, 3 months
Registered June 1, 2001
Not enabled
Protects against DNS spoofing
Unknown
2620:12a:8000::2
CSC Corporate Domains, Inc.
Expiry timeline
Recommended actions
- Domain has EXPIRED — renew immediately to avoid total site outage
- 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