Digital exposure report
teva.com
Good shape, with a few gaps worth closing this quarter.
Scanned: 2026-11-20 07:34 UTC
Full coverage: every applicable check was assessed.
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://teva.com/ | grep -i "Content-Security-Policy"
- 2.
Stop browsers from guessing file types
This removes one way a file could be treated as something it is not.
Who can fix it: Your website developer or web host
How to verify after the fix
curl -sIL https://teva.com/ | grep -i "X-Content-Type-Options"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- teva.com
- Website request
- GET https://teva.com/ → https://www.teva.com/
- Scan time
- 2026-11-20 07:34:31 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- None. Every applicable check was assessed.
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 | 29/30 | 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 | 15/15 | The domain's infrastructure is well hardened. |
Fix priorities
- 1.MediumCSP — protection from script injection · Hardening gap+8
- 2.LowX-Content-Type-Options · Hardening gap+4
- 3.LowReferrer-Policy · Hardening gap+3
- 4.LowPermissions-Policy · Hardening gap+2
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 9/10An authorized sender list is defined; mail from other servers is flagged as suspicious.
~all (softfail) — acceptable when combined with enforced DMARC. 1 of 10 DNS lookups.
v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all$ dig +short TXT teva.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; fo=1; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com
$ dig +short TXT _dmarc.teva.com
DKIM — digital signature on email
Passed · Severity: OK · 5/5A DKIM public key is published. On its own this doesn't prove outgoing mail is signed or aligned with your From domain.
DKIM public key found for selector: default. Confirm signing with dkim=pass in a sent message's Authentication-Results.
default._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzvGFzNdsQngfRoOC0/94wZklOnxy…
$ dig +short TXT default._domainkey.teva.com
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
2 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
10 mxa-00352c01.gslb.pphosted.com 10 mxb-00352c01.gslb.pphosted.com
$ dig +short MX teva.com
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://teva.com/ returned HTTP 403 (final URL: https://www.teva.com/). Client-side certificate validation passed.
HTTP 403 Final URL: https://www.teva.com/
$ curl -sIL https://teva.com/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 308 → https://teva.com/
HTTP 308 Location: https://teva.com/
$ curl -sI http://teva.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: DigiCert, expiring 2027-05-22 (183 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: DigiCert Valid from: 2026-11-05 Valid until: 2027-05-22 Names: *.teva.com, teva.com Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect teva.com:443 -servername teva.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=63072000 (730 days), includeSubDomains, preload. ≥ 180 days recommended.
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
$ curl -sIL https://teva.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://teva.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://teva.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://teva.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://teva.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://teva.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://teva.com/ | grep -iE "^(server|x-powered-by)"
DNSSEC — signed DNS records
Passed · Severity: OK · 7/7The domain's records are digitally signed and hard to forge.
An AD (Authenticated Data) flag was returned by a validating resolver.
AD = true
$ dig +dnssec teva.com | grep -E "flags:.* ad"
CAA — who may issue certificates
Passed · Severity: OK · 5/5Only authorized certificate authorities can issue certificates for the domain.
CAA records: 0 issue "digicert.com" | 0 issue "letsencrypt.org" | 0 issuewild "digicert.com" | 0 issuewild "letsencrypt.org"
0 issue "digicert.com" 0 issue "letsencrypt.org" 0 issuewild "digicert.com" 0 issuewild "letsencrypt.org"
$ dig +short CAA teva.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.
6 NS servers.
ns10.ultradns2.com ns10.ultradns2.org edns3.ultradns.biz edns3.ultradns.com edns3.ultradns.net edns3.ultradns.org
$ dig +short NS teva.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 rulesNo gaps observed
- PCI DSS v4.01 observed gaps
- NIS2 / vendor due diligenceNo gaps observed
- 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 | teva.com | 146.75.30.137 |
| AAAA | teva.com | — |
| MX | teva.com | 10 mxa-00352c01.gslb.pphosted.com | 10 mxb-00352c01.gslb.pphosted.com |
| NS | teva.com | ns10.ultradns2.com | ns10.ultradns2.org | edns3.ultradns.biz | edns3.ultradns.com | edns3.ultradns.net | edns3.ultradns.org |
| TXT | teva.com | _czp9j7k1abxrb2wktr3jhq9yi3gakex | _j0xzt5pfyn1g1sqslfcppfo1369swey | klaviyo-site-verification=RUaGfc | klaviyo-site-verification=Ssa4Rd | klaviyo-site-verification=UjfCmp | klaviyo-site-verification=Vy4MRC | lucid-verification=<fmt9gwezymu1a08s33ju> | v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all | rovag_verification_token=53570EF78AFB4E8FB44914EA22C3BD91 | google-site-verification=jlyT0COZmXlnBCu-ewwWgJTR3yIb34Yn6FqdciqxTeI | google-site-verification=vS0HZ1rUmvj7psdaAoGfT6Pkb1ZH6wegkC9jlyDuEYA |
| TXT | _dmarc.teva.com | v=DMARC1; p=reject; fo=1; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com |
| CAA | teva.com | 0 issue "digicert.com" | 0 issue "letsencrypt.org" | 0 issuewild "digicert.com" | 0 issuewild "letsencrypt.org" |
| DS | teva.com | 54459 13 2 65440fddd840fe110ef28111ec1aa3d3f3275285ddadacc93df13aa1a7c50486 |