Digital exposure report
webex.com
Moderate exposure. There are gaps an attacker could exploit — fix them soon.
Scanned: 2026-11-19 02:59 UTC
Partial coverage: the score is based on 95% of applicable check weight. 1 unverified check(s) are excluded, not counted as failures.
What to do first
- 1.
Limit what scripts your pages are allowed to run
This adds one layer of protection against injected scripts.
Who can fix it: Your website developer or web host
How to verify after the fix
curl -sIL https://webex.com/ | grep -i "Content-Security-Policy"
- 2.
Turn on DNS signing for your domain
Signing helps resolvers detect forged answers about your domain.
Who can fix it: Your domain registrar or DNS provider
How to verify after the fix
dig +short DS webex.com
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- webex.com
- Website request
- GET https://webex.com/ → https://www.webex.com/
- Scan time
- 2026-11-19 02:59:39 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- DKIM — digital signature on email · Not detected (common selectors only)
This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.
Score by category
| Email security | 25/25 | Spoofing email from this domain is hard. |
| Encryption & certificate | 25/25 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | 13/30 | Several browser hardening headers are missing, which removes layers of protection against script injection and framing. |
| DNS infrastructure | 8/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.MediumDNSSEC — signed DNS records · Hardening gap+7
- 2.MediumCSP — protection from script injection · Hardening gap+8
- 3.LowX-Content-Type-Options · Hardening gap+4
- 4.LowReferrer-Policy · Hardening gap+3
- 5.LowPermissions-Policy · Hardening gap+2
To verify
Couldn't be confirmed from public data, so excluded from the score. Checking them clarifies your posture; it doesn't guarantee a score change.
- DKIM — digital signature on email
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 10/10An authorized sender list is defined and mail from other servers is rejected.
Valid SPF record with -all. 1 of the 10 allowed DNS lookups.
v=spf1 redirect=_spf.webex.com
$ dig +short TXT webex.com
DMARC — anti-spoofing policy
Passed · Severity: OK · 15/15Forged email in the company's name is blocked by mail servers.
Policy p=reject.
v=DMARC1; p=reject; pct=100; rua=mailto:mail-reports-webex@cisco.com
$ dig +short TXT _dmarc.webex.com
DKIM — digital signature on email
Not detected (common selectors only) · Severity: OK · Not scoredNo DKIM key was found under the common selectors we probed. That doesn't mean DKIM is missing — selectors can't be listed from public DNS. Not scored.
A missing name for a probed selector (NXDOMAIN/NODATA) only means that selector isn't published. DKIM is marked unverified and excluded from the score. Check a sent message's Authentication-Results for dkim=pass and its s= selector.
Selectors checked: google, selector1, selector2, default, k1, s1, s2, dkim, mail, smtp — no key found google._domainkey: nxdomain selector1._domainkey: nxdomain selector2._domainkey: nxdomain default._domainkey: nxdomain k1._domainkey: nxdomain s1._domainkey: nxdomain s2._domainkey: nxdomain dkim._domainkey: nxdomain mail._domainkey: nxdomain smtp._domainkey: nxdomain
$ dig +short TXT google._domainkey.webex.com
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
3 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
10 alln-mx-01.cisco.com 30 aer-mx-01.cisco.com 20 rcdn-mx-01.cisco.com
$ dig +short MX webex.com
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://webex.com/ returned HTTP 403 (final URL: https://www.webex.com/). Client-side certificate validation passed.
HTTP 403 Final URL: https://www.webex.com/
$ curl -sIL https://webex.com/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 302 → https://webex.com/
HTTP 302 Location: https://webex.com/
$ curl -sI http://webex.com/ | grep -iE "^(HTTP|location)"
SSL/TLS certificate validity
Passed · Severity: OK · 8/8The certificate was accepted by a validating TLS client at scan time.
Live TLS handshake succeeded. Latest issuance in CT logs: IdenTrust Services, expiring 2027-04-27 (158 days). CT shows issued certificates, not necessarily the one served — confirm dates with the verify command.
Live TLS handshake: certificate accepted CT logs (context only, not scored): Issuer: IdenTrust Services Valid from: 2026-10-10 Valid until: 2027-04-27 Names: ciscoaisummit.com, contractdocuments.webex.com, webex.ai, webex.ca, webex.co.in, webex.co.it Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect webex.com:443 -servername webex.com 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Passed · Severity: OK · 8/8Browsers are told to always use an encrypted connection to the site.
max-age=31536000 (365 days), includeSubDomains. ≥ 180 days recommended.
Strict-Transport-Security: max-age=31536000 ; includeSubDomains
$ curl -sIL https://webex.com/ | grep -i "Strict-Transport-Security"
CSP — protection from script injection
Failed · Severity: Medium · Hardening gap · 0/8Missing Content-Security-Policy header: this removes one layer of protection against script injection.
No Content-Security-Policy header found.
Content-Security-Policy: (missing)
$ curl -sIL https://webex.com/ | grep -i "Content-Security-Policy"
- First publish Content-Security-Policy-Report-Only — it blocks nothing, it only reports.
- Collect violations for a week or two and tune the policy to your legitimate sources.
- Switch to the Content-Security-Policy header and replace 'unsafe-inline' with a nonce or hash.
/* Content-Security-Policy-Report-Only: default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'
Safety: This change is made in your server/CDN settings. Test on staging before production. An overly strict CSP will break scripts — that's why you start in Report-Only mode.
Clickjacking protection
Passed · Severity: OK · 5/5The site can't be embedded by foreign sites.
X-Frame-Options: SAMEORIGIN
X-Frame-Options: SAMEORIGIN
$ curl -sIL https://webex.com/ | grep -i "X-Frame-Options"
X-Content-Type-Options
Failed · Severity: Low · Hardening gap · 0/4The browser may interpret files as code unintentionally.
Missing X-Content-Type-Options: nosniff header (MIME sniffing).
X-Content-Type-Options: (missing)
$ curl -sIL https://webex.com/ | grep -i "X-Content-Type-Options"
- Add X-Content-Type-Options: nosniff to every response.
/* X-Content-Type-Options: nosniff
Safety: This change is made in your server/CDN settings. Test on staging before production.
Referrer-Policy
Failed · Severity: Low · Hardening gap · 0/3Internal URLs (including parameters) may leak to external sites.
Referrer-Policy is missing; the browser will use its default.
Referrer-Policy: (missing)
$ curl -sIL https://webex.com/ | grep -i "Referrer-Policy"
- Set Referrer-Policy: strict-origin-when-cross-origin.
/* Referrer-Policy: strict-origin-when-cross-origin
Safety: This change is made in your server/CDN settings. Test on staging before production.
Permissions-Policy
Needs attention · Severity: Low · Hardening gap · 0/2Access to sensitive features like the camera and location isn't restricted.
Missing Permissions-Policy header.
Permissions-Policy: (missing)
$ curl -sIL https://webex.com/ | grep -i "Permissions-Policy"
- Disable browser features the site doesn't need (camera, microphone, geolocation).
/* Permissions-Policy: camera=(), microphone=(), geolocation=()
Safety: This change is made in your server/CDN settings. Test on staging before production. Don't disable a feature the site actually uses.
Software version disclosure
Passed · Severity: OK · unscoredThe server doesn't disclose software versions.
No version numbers found in the Server / X-Powered-By headers.
server: cloudflare x-powered-by: (missing)
$ curl -sIL https://webex.com/ | grep -iE "^(server|x-powered-by)"
DNSSEC — signed DNS records
Needs attention · Severity: Medium · Hardening gap · 0/7The domain's records aren't signed, so in some scenarios users could be redirected to a forged server.
No DS record is published at the parent zone, so there's no DNSSEC chain of trust for this zone.
AD = false DS webex.com: NODATA
$ dig +short DS webex.com
- Enable DNSSEC at your DNS provider (one click at most providers).
- Copy the DS record your provider generates to your domain registrar.
- Wait for propagation and verify with DNSViz.
dig +dnssec webex.com SOA delv webex.com
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. A wrong DS record at the registrar will make the domain stop resolving — copy it exactly from the provider.
CAA — who may issue certificates
Passed · Severity: OK · 5/5Only authorized certificate authorities can issue certificates for the domain.
CAA records: 0 issue "amazon.com" | 0 issue "digicert.com" | 0 issue "globalsign.com" | 0 issue "identrust.com" | 0 issue "letsencrypt.org" | 0 issue "pki.goog" | 128 iodef "mailto:infosec@cisco.com" | 128 issuewild "digicert.com" | 128 issuewild "identrust.com"
0 issue "amazon.com" 0 issue "digicert.com" 0 issue "globalsign.com" 0 issue "identrust.com" 0 issue "letsencrypt.org" 0 issue "pki.goog" 128 iodef "mailto:infosec@cisco.com" 128 issuewild "digicert.com" 128 issuewild "identrust.com"
$ dig +short CAA webex.com
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
2 NS servers.
ns1.as13445.net ns2.as13445.net
$ dig +short NS webex.com
Indicative alignment
Best-practice mapping of public findings to common frameworks. Passive scanning tests public configuration only; it doesn't prove compliance or a violation.
- Google & Yahoo sender rules1 unverified
- PCI DSS v4.01 observed gaps
- NIS2 / vendor due diligence1 observed gaps
- SOC 2 / ISO 27001 baseline2 observed gaps
Indicative alignment only, based on public configuration. It doesn't establish whether a framework applies to you, and it isn't legal advice, an audit or a certification.
Public DNS records
| A | webex.com | 144.196.130.69 |
| AAAA | webex.com | 2607:fcf0:2100:0:144:196:130:69 |
| MX | webex.com | 10 alln-mx-01.cisco.com | 30 aer-mx-01.cisco.com | 20 rcdn-mx-01.cisco.com |
| NS | webex.com | ns1.as13445.net | ns2.as13445.net |
| TXT | webex.com | MS=ms61160488 | MS=ms67549965 | MS=ms74589643 | MS=ms93683787 | slimtesttxt20170824001 | slimtesttxt20170824002 | ms93683787.msv1.invalid | im3l8j2k42u788bccbdisp5li | 9cef3rr776cnjs1cu53q6hrium | lqucp0f6u7alqi7kgrjo5vsov5 | lrg2pr6u4ubansuv47jtmmfd3p | v=spf1 redirect=_spf.webex.com | _4mb09s73v6a9wckdb66vo493hjjaors | _6ik2pmf86xptsbgsszcs655ujokc92i | _ayh0pajfqje3pjs2pm116pd355r34v0 | _g5c6ucjoc163k9fpvz542l1d1dfrpqo | _ulktgfpu90kjp0ycysgm6rs81a9jw0c | QuoVadis=5a740d9e-6664-4d4c-8d87-716da9d530a7 | QuoVadis=c1bf1f71-e21f-4ef5-92d9-3285c488767a | QuoVadis=eed4c791-aa21-4b45-8c91-2d83a93af871 | amazonses:n3XkGYyvmC8SrhX+CqICjY4eWnyKFwPo6mdHTMsmeu4= | google-site-verification=BEWshakJYRMouwSQKX3vk5144-qUL1wwUWLU-XtfQ | google-site-verification=3NhfQ1u_2ogGy3CA8qlIfFtMlW_nhx-VO85vAhT15a0 | google-site-verification=BEWshakJYRMouwSQKX_3vk5_144-qUL1wwUWLU-XtfQ | google-site-verification=D1PXZV2EBUXGvgJdUWr3cahNprUgckDpzo8MgniDQHk | google-site-verification=JrxFkdPqnLrmVyx1PTP1bKqRT0nxPR4yJKPnswmQiwc | google-site-verification=RzBAdlNK125jocPINSM2ZOszpndsXj05vWe7wW2S0SQ | google-site-verification=Z4Iwv_W8wkGKrlaPKLdcm3C_LDCydAJD6z3L1MAP7DI | google-site-verification=_t-SfLHtBYLmxc40wrfAo8B9KwGg0jzSx2I1uVBbXLk | google-site-verification=fHXTAHXgtW5_Dzt4PHZKGF2PAI0r6PEHqmHJbkxo4_k | google-site-verification=qXk-s_bdPaqiuaDN9jJCQjvNyw_hVkxXDhkm-1mZn14 | google-site-verification=t2i1Swk8XPQDj6Llz_4Uxu3OKL3wfO_aaxYylFmQ8MU |
| TXT | _dmarc.webex.com | v=DMARC1; p=reject; pct=100; rua=mailto:mail-reports-webex@cisco.com |
| CAA | webex.com | 0 issue "amazon.com" | 0 issue "digicert.com" | 0 issue "globalsign.com" | 0 issue "identrust.com" | 0 issue "letsencrypt.org" | 0 issue "pki.goog" | 128 iodef "mailto:infosec@cisco.com" | 128 issuewild "digicert.com" | 128 issuewild "identrust.com" |
| DS | webex.com | — |