Digital exposure report
illusive.com
Moderate exposure. There are gaps an attacker could exploit — fix them soon.
Scanned: 2026-11-19 02:59 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
Tell receiving mail servers how to treat fake email from your domain
Without this policy, inboxes have less guidance for spotting messages that impersonate you.
Who can fix it: Your email provider, together with whoever manages your DNS
How to verify after the fix
dig +short TXT _dmarc.illusive.com
- 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 illusive.com
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- illusive.com
- Website request
- GET https://illusive.com/ → https://www.proofpoint.com/us/illusive-is-now-proofpoint
- Scan time
- 2026-11-19 02:59:44 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 | 18/30 | Spoofing email in the company's name is possible in some cases. |
| Encryption & certificate | 25/25 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | 25/30 | The site instructs browsers to block common attacks. |
| DNS infrastructure | 8/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.MediumDMARC — anti-spoofing policy · Hardening gap+11
- 2.MediumDNSSEC — signed DNS records · Hardening gap+7
- 3.LowPermissions-Policy · Hardening gap+2
- 4.LowCSP — protection from script injection · Hardening gap+3
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:_spf.google.com ~all
$ dig +short TXT illusive.com
DMARC — anti-spoofing policy
Needs attention · Severity: Medium · Hardening gap · 4/15DMARC is in monitoring mode only — forged email still reaches recipients.
Policy p=none. p=none collects reports but does not protect. No rua — no reports on spoofing attempts are received.
v=DMARC1; p=none; sp=none; ruf=mailto:it@illusive.com; rf=afrf; pct=100; ri=86400
$ dig +short TXT _dmarc.illusive.com
- Step 1 (monitoring, no effect on mail): publish p=none with an rua address to receive reports.
- Step 2: analyze reports for 2–4 weeks and make sure every legitimate sender passes SPF/DKIM.
- Step 3: move to p=quarantine, and finally to p=reject.
_dmarc.illusive.com. TXT "v=DMARC1; p=none; rua=mailto:dmarc@illusive.com; fo=1"
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. Jumping straight to reject without a monitoring phase can block legitimate mail.
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: google. Confirm signing with dkim=pass in a sent message's Authentication-Results.
google._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAspeDwW2EPIvAAX6fDI65soJIdLnv…
$ dig +short TXT google._domainkey.illusive.com
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
4 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
15 mx0a-00148501.pphosted.com 10 mxb-00148501.gslb.pphosted.com 10 mxa-00148501.gslb.pphosted.com 15 mx0b-00148501.pphosted.com
$ dig +short MX illusive.com
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://illusive.com/ returned HTTP 200 (final URL: https://www.proofpoint.com/us/illusive-is-now-proofpoint). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.proofpoint.com/us/illusive-is-now-proofpoint
$ curl -sIL https://illusive.com/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://www.proofpoint.com/us/illusive-is-now-proofpoint
HTTP 301 Location: https://www.proofpoint.com/us/illusive-is-now-proofpoint
$ curl -sI http://illusive.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: Sectigo, expiring 2027-03-30 (131 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: Sectigo Valid from: 2026-09-13 Valid until: 2027-03-30 Names: blog.illusive.com, go.illusive.com, illusive.com, www.illusive.com Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect illusive.com:443 -servername illusive.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, preload. ≥ 180 days recommended.
Strict-Transport-Security: max-age=31536000, includeSubDomains, preload
$ curl -sIL https://illusive.com/ | grep -i "Strict-Transport-Security"
CSP — protection from script injection
Needs attention · Severity: Low · Hardening gap · 5/8A script policy exists, but it's permissive and offers only partial protection.
script-src includes: 'unsafe-inline', 'unsafe-eval' — weakens XSS protection.
Content-Security-Policy: default-src 'self' blob:; script-src 'self' 'unsafe-inline' 'unsafe-eval' blob: https://www.google-analytics.com https://www.googleoptimize.com https://www.googletagmanager.com https://munchkin.marketo.net https://app-abj.marketo.com https://www.googleadservices.com https://googleads.g.doubleclick.net https://geoip-js.com https://ads.avocet.io https://trk.techtarget.com https://j.6sc.co https://tags.srv.stackadapt.com https://ads.avct.cloud https://js.driftt.com https://js-agent.newrelic.com https://bam.nr-data.net https://cdn.jsdelivr.net https://js.adsrvr.org https://go.affec.tv https://bat.bing.com https://s7.addthis.com https://m.addthis.com https://z.moatads.com https://snap.licdn.com https://tracking.g2crowd.com https://connect.facebook.net *.visualwebsiteoptimizer.com https://app.vwo.com *.sharethis.com https://unpkg.com https://d1hgczpbubj217.cloudfront.net https://app-static.turtl.co https://js.zi-scripts.com *.mutinycdn.com https://www.clarity.ms https://scripts.clarity.ms *.roundprinceweb.com https://www.redditstatic.com https://go.proofpoint.com https://www.google.com https://www.gstatic.com https://www.buzzsprout.com *.vimeocdn.com https://storage.googleapis.com https://js.navattic.com *.qualified.com https://wpaassets.blob.core.windows.net *.youtube.com vimeo.com *.vimeo.com cdn.cookielaw.org *.onetrust.com *.proofpoint.com https://live.rezync.com https://script.supademo.com https://cdn.pagesense.io https://bzrcdn.openai.com https://tags.srv.stackadapt.com https://*.stackadapt.com https://*.srv.stackadapt.com; object-src 'self'; style-src 'self' 'unsafe-inline' *; img-src 'self' 'unsafe-inline' data: blob: *; media-src 'self' *.qualified.com; frame-src 'self' 'unsafe-inline' *; frame-ancestors 'self' app.mutinyhq.com; child-src 'self' 'unsafe-inline' blob: *.qualified.com; worker-src 'self' blob:; font-src 'self' 'unsafe-inline' data: *; connect-src 'self' 'unsafe-inline' *; report-uri /report-csp-violation
$ curl -sIL https://illusive.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 frame-ancestors 'self' app.mutinyhq.com
X-Frame-Options: SAMEORIGIN CSP frame-ancestors: 'self' app.mutinyhq.com
$ curl -sIL https://illusive.com/ | grep -i "X-Frame-Options"
X-Content-Type-Options
Passed · Severity: OK · 4/4The browser won't guess file types in a way that could execute code.
nosniff is set.
X-Content-Type-Options: nosniff
$ curl -sIL https://illusive.com/ | grep -i "X-Content-Type-Options"
Referrer-Policy
Passed · Severity: OK · 3/3Internal URLs don't leak to external sites.
Referrer-Policy: origin-when-cross-origin
Referrer-Policy: origin-when-cross-origin
$ curl -sIL https://illusive.com/ | grep -i "Referrer-Policy"
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://illusive.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://illusive.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 illusive.com: NODATA
$ dig +short DS illusive.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 illusive.com SOA delv illusive.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 "thawte.com" | 0 issue "amazonaws.com" | 0 issue "comodo.com" | 0 issuewild "amazontrust.com" | 0 issuewild "awstrust.com" | 0 issue "awstrust.com" | 0 issue "amazon.com" | 0 issuewild "amazon.com" | 0 issuewild "amazonaws.com" | 0 issue "amazontrust.com"
0 issue "thawte.com" 0 issue "amazonaws.com" 0 issue "comodo.com" 0 issuewild "amazontrust.com" 0 issuewild "awstrust.com" 0 issue "awstrust.com" 0 issue "amazon.com" 0 issuewild "amazon.com" 0 issuewild "amazonaws.com" 0 issue "amazontrust.com"
$ dig +short CAA illusive.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.
ns1.proofpoint.com ns3.proofpoint.com pdns99.ultradns.biz pdns99.ultradns.com pdns99.ultradns.net pdns99.ultradns.org
$ dig +short NS illusive.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 observed gaps
- PCI DSS v4.01 observed gaps
- NIS2 / vendor due diligence2 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 | illusive.com | 45.60.171.207 | 45.60.151.207 |
| AAAA | illusive.com | — |
| MX | illusive.com | 15 mx0a-00148501.pphosted.com | 10 mxb-00148501.gslb.pphosted.com | 10 mxa-00148501.gslb.pphosted.com | 15 mx0b-00148501.pphosted.com |
| NS | illusive.com | ns1.proofpoint.com | ns3.proofpoint.com | pdns99.ultradns.biz | pdns99.ultradns.com | pdns99.ultradns.net | pdns99.ultradns.org |
| TXT | illusive.com | 01A73977F1 | MS=ms86428260 | v=spf1 include:_spf.google.com ~all | google-site-verification=fu-Zhyt_bJfSYrc88CBjFm7lq_KAjwbbk9TJ0P5pkQc | atlassian-domain-verification=1aZSKs6N/vTruQtGayZqTdKfy6MFYdAqvbaG4BG1CSHzEU2D8lrbSbJ9lld8fNQt |
| TXT | _dmarc.illusive.com | v=DMARC1; p=none; sp=none; ruf=mailto:it@illusive.com; rf=afrf; pct=100; ri=86400 |
| CAA | illusive.com | 0 issue "thawte.com" | 0 issue "amazonaws.com" | 0 issue "comodo.com" | 0 issuewild "amazontrust.com" | 0 issuewild "awstrust.com" | 0 issue "awstrust.com" | 0 issue "amazon.com" | 0 issuewild "amazon.com" | 0 issuewild "amazonaws.com" | 0 issue "amazontrust.com" |
| DS | illusive.com | — |