Skip to content
https://zoom.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

C
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.zoom.com/
200https://zoom.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://zoom.com/ https://www.zoom.com

Use 301 (permanent) instead of 302 (temporary)

B
TLS Certificate Expiry & Recommendations
67 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

67
days left
0d 30d 60d 90d+

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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 Records
1 A records, 104 ms lookup
PASS
1 A records, 104 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 170.114.0.12
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-481.awsdns-60.com, ns-1861.awsdns-40.co.uk, ns-968.awsdns-57.net, ns-1473.awsdns-56.org
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 104 ms
Got: 104 ms
A170.114.0.12
AAAA
CNAME
NSns-481.awsdns-60.com, ns-1861.awsdns-40.co.uk, ns-968.awsdns-57.net, ns-1473.awsdns-56.org
MX
10 mxb-00569201.gslb.pphosted.com
10 mxa-00569201.gslb.pphosted.com
TXT
v=DMARC1; p=reject; ri=3600; rua=mailto:sesbounce@zoom.us,mailto:dmarc_rua@email...
Account Engagement emails pass SPF automatically, but we recommend setting it up...
s4pcsx9yj8thv2vb6gh6ryydd05zvcr9
MS=ms37328709
google-site-verification=yiEieNiefNiSqgLq5rY_z_HyZ4HjDX_0yJlJME33_jA
pardot84442=66c53a10788b0276a0880d5d21a71b44df9a3c5692e545acce46644ea73b1cc6
HaFoSdUeCSdJo9U8lG@NWZ6vnoRltUteEAl&yuY$$eE25sKJguFH58Lss%9@e73OK#XigH^i3mCDjax&...
nintex.5e7289cea709bf0d10e77561
anthropic-domain-verification-mzg56s=vpNmDWwfLVSNLFCCywtMb6Hns
h1-domain-verification=5yw85Ewx1obuckMSkZQokfDYewnzdBw9JqKmZWMXqFs2F3cq
spycloud-domain-verification=25022702-4ddc-4746-be61-c2baf9b129e9
dropbox-domain-verification=9dklsyoh0ul
stripe-verification=56bc5cf2da44b2033da49b45ed3789209db29432268975666693a750ecfd...
google-site-verification=k1nKdEppgAfcBIQjwlOflCohpA7U4fc4PhIhwNrHf1c
google-site-verification=wa9RTNAmvbZSMxaJqaXeIjJ7NHBNN7xCuBKD1sZuDfY
adobe-idp-site-verification=7116ab50a89b2c2402382aea3362209410eac90f2a590f358ce1...
apple-domain-verification=bzL9n7DPRh8nIyQU
atlassian-domain-verification=o4YG+mXlOE6uTJb7uGimcl9DJZnVg4aimBCf/4UrplRJvMk84J...
smartsheet-site-validation=WHwoPMjyyUbL71JC9sECier4NQyyIVaL
sending_domain84442=f09895e4aa7f6a4550421683b7e5d817ba38189dcc438f14daf27125a533...
06n3zb0ycwlgmqr4c9l9frn370klrcvv
SPF v=spf1 mx include:%{ir}.%{v}.%{d}.spf.has.pphosted.com include:_spf.google.com i...
docker-verification=5d64ad19-0f15-46a0-9bc3-817e577eb276
CAALookup not available with standard resolver
Resolved in 104 ms

Multiple A records provide failover if one server goes down.

Why this matters

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.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 549 ms total
PASS
1 redirect(s), 549 ms total
Info::
Single redirect
Got: https://zoom.com → https://www.zoom.com (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://zoom.com
Info::
Redirect overhead: 549 ms total
Got: 549 ms

https://zoom.com

385 ms · HTTP/1.1

302

https://www.zoom.com

164 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://zoom.com302385 msHTTP/1.1zoom
2https://www.zoom.com200164 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

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

A+
Crawlability
robots.txt present, sitemap with 5454 URLs
PASS
robots.txt present, sitemap with 5454 URLs
Info::
robots.txt is present
Got: 2005 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 5454 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2005 B Sitemaps referenced 1 User-agents *, LinkedInBot, facebookexternalhit, Twitterbot, PinterestBot, InstagramBot, Slackbot, WhatsApp, Googlebot, redditbot, Tumblr, TikTokBot, Snapchat Blocking No — crawling allowed
User-Agent: *
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: /wc/*
Disallow: /web/*
Disallow: /share*
Disallow: /support*
Disallow: /j/*
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: /*?

User-agent: Googlebot
Allow: /join

User-agent: LinkedInBot
Allow: /webinar/register/*
Allow: /webinar/registerevent/*
Allow: /meeting/register/*

User-agent: facebookexternalhit
Allow: /webinar/register/*
Allow: /webinar/registerevent/*
Allow: /meeting/register/*

User-agent: Twitterbot
Allow: /webinar/register/*
Allow: /webinar/registerevent/*
Allow: /meeting/register/*

User-agent: PinterestBot
Allow: /webinar/register/*
Allow: /webinar/registerevent/*
Allow: /meeting/register/*

User-agent: InstagramBot
Allow: /webinar/register/*
Allow: /webinar/registerevent/*
Allow: /meeting/register/*

User-agent: Slackbot
Allow: /webinar/register/*
Allow: /webinar/registerevent/*
Allow: /meeting/register/*

User-agent: WhatsApp
Allow: /webinar/register/*
Allow: /webinar/registerevent/*
Allow: /meeting/register/*

User-agent: redditbot
Allow: /webinar/register/*
Allow: /webinar/registerevent/*
Allow: /meeting/register/*

User-agent: Tumblr
Allow: /webinar/register/*
Allow: /webinar/registerevent/*
Allow: /meeting/register/*

User-agent: TikTokBot
Allow: /webinar/register/*
Allow: /webinar/registerevent/*
Allow: /meeting/register/*

User-agent: Snapchat
Allow: /webinar/register/*
Allow: /webinar/registerevent/*
Allow: /meeting/register/*

Sitemap: https://zoom.us/sitemap.xml
A+
Domain Intelligence
zoom.com — via MarkMonitor Inc., 27 years, 4 months old, hosted on AWS
PASS
zoom.com — via MarkMonitor Inc., 27 years, 4 months old, hosted on AWS
Info::
Domain registered until Dec 2, 2027 (1 years, 7 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: MarkMonitor Inc.
Warning::
Registrar lock is NOT enabled
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.
Info::
Hosting: AWS
Got: AS14618
Domain expiry

506 days

December 2, 2027

SSL certificate

67 days

Issued by DigiCert Inc

Domain age

27 years, 4 months

Registered April 22, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

170.114.0.12

Registrar

MarkMonitor Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created April 22, 1999 (27 years, 4 months ago)
Expires December 2, 2027 (1 years, 7 months)
Last Updated October 31, 2025
Name Servers ns-1473.awsdns-56.org, ns-1861.awsdns-40.co.uk, ns-481.awsdns-60.com, ns-968.awsdns-57.net
DNSSEC Not enabled
Hosting
IP Address 170.114.0.12
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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.

Why this matters

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

A
HTTP Probe Timing
Total 419 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
29 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
97 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
196 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
420 ms
Total Time Total request time from DNS lookup through full response.
420 ms

Connection waterfall

DNS Lookup 29 ms TCP Connect 97 ms TLS Handshake 196 ms Server Processing 98 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback