Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FIPv6 ReadinessActionIPv6 records exist but unreachableFIX
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.
Learn more ▾ ▴
Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.
Source: RFC 8305 (Happy Eyeballs)
BTLS Certificate Expiry & Recommendations119 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- 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, 59 ms lookupPASS
| A | 170.114.78.80 |
| AAAA | 2407:30c0:183::aa72:4e50 |
| CNAME | — |
| NS | — |
| MX | — |
| TXT | — |
| 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.
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.
Learn more ▾ ▴
SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.
Source: RFC 7208 (SPF)
A+Redirect ChainNo redirects — direct accessPASS
https://www.zoom.com
172 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.zoom.com | 200 | 172 ms | HTTP/1.1 | cloudflare |
A+Crawlabilityrobots.txt present, sitemap with 18 URLsPASS
User-agent: *
Allow: /*.js*
Allow: /*.css*
Disallow: /episerver/cms
Disallow: /util/
Disallow: /epiutil/
Disallow: */bin/
Disallow: */app_data/
Disallow: */search?
Disallow: */search-results
Disallow: /episerver/cms
Disallow: /util/
Disallow: /epiutil/
Disallow: */bin/
Disallow: */app_data/
Disallow: */search-results
Disallow: */components/
Disallow: */qa/
Disallow: */~/
Disallow: */siteassets/
Disallow: */page-templates/
Disallow: /download/*/Zoom_launcher.exe
Disallow: /download/*/zoomusLauncher.zip
Disallow: /docs/image/new/brand/outdated/
Disallow: /docs/doc/2-Page-All-Products.pdf
Disallow: /docs/doc/zoom-apps-security-privacy-faq.pdf
Disallow: /docs/doc/zoom-apps-data-management.pdf
Disallow: /j/
Disallow: /wc/
Disallow: /web/
Disallow: /share*
Disallow: /support*
Disallow: /z/
Disallow: /s/
Disallow: /u/
Disallow: /w/
Disallow: /e/
Disallow: /account*
Disallow: /start*
Disallow: /postattendee*
Disallow: /rec/
Disallow: /register*
Disallow: /webinar/register/
Disallow: /webinar/registerevent/
Disallow: /meeting/register/
Disallow: /*oauth_signin
Disallow: /my/
Disallow: /download2*
Disallow: */link/
Disallow: /epi-util/
sitemap: https://www.zoom.com/sitemap_index.xml
- https://www.zoom.com/sitemap-en.xml
- https://www.zoom.com/sitemap-de.xml
- https://www.zoom.com/sitemap-fr.xml
- https://www.zoom.com/sitemap-es.xml
- https://www.zoom.com/sitemap-sv.xml
- https://www.zoom.com/sitemap-nl.xml
- https://www.zoom.com/sitemap-vi.xml
- https://www.zoom.com/sitemap-tr.xml
- https://www.zoom.com/sitemap-ru.xml
- https://www.zoom.com/sitemap-pt.xml
- https://www.zoom.com/sitemap-pl.xml
- https://www.zoom.com/sitemap-ko.xml
- https://www.zoom.com/sitemap-ja.xml
- https://www.zoom.com/sitemap-it.xml
- https://www.zoom.com/sitemap-id.xml
- https://www.zoom.com/sitemap-zh-tw.xml
- https://www.zoom.com/sitemap-zh-cn.xml
- https://www.zoom.com/sitemap-blog.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: www
HTTP → HTTPS
Consistent
A+Domain Intelligencezoom.com — via MarkMonitor Inc., 27 years, 4 months old, hosted on AWSPASS
472 days
December 2, 2027
119 days
Issued by DigiCert Inc
27 years, 4 months
Registered April 22, 1999
Not enabled
Protects against DNS spoofing
AWS
ASN AS14618
170.114.0.14
MarkMonitor Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
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