Digital exposure report
mparticle.com
Good shape, with a few gaps worth closing this quarter.
Scanned: 2026-11-19 02:59 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
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 mparticle.com
- 2.
Limit what your site shares when visitors click links
This reduces how much page address detail is passed to other websites.
Who can fix it: Your website developer or web host
How to verify after the fix
curl -sIL https://mparticle.com/ | grep -i "Referrer-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- mparticle.com
- Website request
- GET https://mparticle.com/ → https://www.rokt.com/rokt-mparticle/platform
- Scan time
- 2026-11-19 02:59:37 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 | 27/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 | 21/30 | Some browser protections are missing. |
| 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.LowReferrer-Policy · Hardening gap+3
- 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. 5 of 10 DNS lookups.
v=spf1 ip4:54.208.176.96/32 include:_spf.google.com include:sendgrid.net include:_spf.salesforce.com include:mail.zendesk.com include:3853670.spf10.hubspotemail.net ~all
$ dig +short TXT mparticle.com
DMARC — anti-spoofing policy
Passed · Severity: OK · 13/15Forged email in the company's name is sent to the spam folder.
Policy p=quarantine. p=quarantine — consider moving to p=reject.
v=DMARC1; p=quarantine; sp=quarantine; fo=1; ruf=mailto:rokt-t@dmarc.report-uri.com; rua=mailto:rokt-t@dmarc.report-uri.com;
$ dig +short TXT _dmarc.mparticle.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: google, k1, s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
google._domainkey: v=DKIM1;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxJ3pn2PD7l8/RHzr/WhxKeZn+C5tuw… k1._domainkey: k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDRAc5xdUwAczVkWUjEAL8QAR4gfq8kSluLuonnclzwg… s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2kY/8aJd4+jO5z9Mjrt+GT85jnsZnGQ8… s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC+om0KQ3hahYTfAAF6NZOUeTj4ZQHcEpj9Ie2N…
$ dig +short TXT google._domainkey.mparticle.com
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
5 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
20 aspmx.l.google.com 21 alt1.aspmx.l.google.com 22 alt2.aspmx.l.google.com 23 alt3.aspmx.l.google.com 24 alt4.aspmx.l.google.com
$ dig +short MX mparticle.com
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://mparticle.com/ returned HTTP 200 (final URL: https://www.rokt.com/rokt-mparticle/platform). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.rokt.com/rokt-mparticle/platform
$ curl -sIL https://mparticle.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.rokt.com/rokt-mparticle/platform
HTTP 301 Location: https://www.rokt.com/rokt-mparticle/platform
$ curl -sI http://mparticle.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: GoDaddy, expiring 2027-04-23 (155 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: GoDaddy Valid from: 2026-10-07 Valid until: 2027-04-23 Names: mparticle.com Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect mparticle.com:443 -servername mparticle.com 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Passed · Severity: OK · 7/8Browsers are told to always use an encrypted connection to the site.
max-age=31536000 (365 days), no includeSubDomains. ≥ 180 days recommended.
Strict-Transport-Security: max-age=31536000
$ curl -sIL https://mparticle.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: no script-src/default-src — weakens XSS protection.
Content-Security-Policy: frame-ancestors 'self'
$ curl -sIL https://mparticle.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'
X-Frame-Options: SAMEORIGIN CSP frame-ancestors: 'self'
$ curl -sIL https://mparticle.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://mparticle.com/ | grep -i "X-Content-Type-Options"
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://mparticle.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://mparticle.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://mparticle.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 mparticle.com: NODATA
$ dig +short DS mparticle.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 mparticle.com SOA delv mparticle.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 iodef "mailto:security@mparticle.com" | 0 issue "amazon.com" | 0 issue "digicert.com" | 0 issue "globalsign.com" | 0 issue "godaddy.com" | 0 issue "letsencrypt.org" | 0 issuewild "globalsign.com" | 0 issuewild "godaddy.com" | 0 issuewild "letsencrypt.org"
0 iodef "mailto:security@mparticle.com" 0 issue "amazon.com" 0 issue "digicert.com" 0 issue "globalsign.com" 0 issue "godaddy.com" 0 issue "letsencrypt.org" 0 issuewild "globalsign.com" 0 issuewild "godaddy.com" 0 issuewild "letsencrypt.org"
$ dig +short CAA mparticle.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.
4 NS servers.
ns-1447.awsdns-52.org ns-1796.awsdns-32.co.uk ns-206.awsdns-25.com ns-553.awsdns-05.net
$ dig +short NS mparticle.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 diligence1 observed gaps
- SOC 2 / ISO 27001 baseline1 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 | mparticle.com | 151.101.2.133 | 151.101.66.133 | 151.101.130.133 | 151.101.194.133 |
| AAAA | mparticle.com | — |
| MX | mparticle.com | 20 aspmx.l.google.com | 21 alt1.aspmx.l.google.com | 22 alt2.aspmx.l.google.com | 23 alt3.aspmx.l.google.com | 24 alt4.aspmx.l.google.com |
| NS | mparticle.com | ns-1447.awsdns-52.org | ns-1796.awsdns-32.co.uk | ns-206.awsdns-25.com | ns-553.awsdns-05.net |
| TXT | mparticle.com | MS=ms30846526 | _globalsign-domain-verification=OFlRsOmW1e-DddCoc5wa_aq2gpHcL7e710UgPBjCta | _globalsign-domain-verification=b1pmSjP4FyG8hkZunkD3Aoz8tK0FWCje80-YwtLeDU | airtable-verification=a787e431dbb83f2c799756b2c08ee862 | atlassian-domain-verification=q8gQK2RwbpHaDoBWQhaLrFuDXiz8TKKKmdDr8cZc5h9cy4G0N1TlQ8cPdMC30XSZ | canva-site-verification=RJhIxK-EmLSYqMci_mDzpQ | central-9389 | citrix-verification-code=5d00e31d-4945-4a84-b525-c966f21dc866 | docusign=45afb1b7-f187-45e2-a9fd-de34671d3b6c | dropbox-domain-verification=vd4gzw6jznlv | google-site-verification=4f5QnxpTYKP5AsoWdXkfepZl9a0zhrvemHj0Oxy0NJQ | google-site-verification=CXsUhG-7Ts31GEUg8wmal2ONraG0uMxziLjRN5BiZz4 | google-site-verification=Ga46KsKWZAHivHoaoVDB2oXVGAgzq3TcyrA1l7qU2-E | google-site-verification=Hd4WlrwLI5k6Pb6j34Z1lrqoZcmmoeqnRSAMjkXh7bw | google-site-verification=OkQtoY-3lk5u42C5y5GhG2Zv2-lDf9sXa3q03Of7row | h1-domain-verification=iqybC1Wb7Wi1DSHqUPTJTHb1JoP6BWS8DcPbLHeSJyj4FAHt | logmein-domain-confirmation jska7893279jkdhkkjdhas55 | logmein-verification-code=823ea0a5-0ed6-4336-b09a-9fb76d677555 | onetrust-domain-verification=170d658270ba4ff8b44c470874c0952f | pardot398262=707e44cd4a36bd5125ec3260dc2c119728fa8f3fbf907bedbed30862d60c3e13 | postman-domain-verification=6428b9b4c7f5eb5ec1f87afc0cb79ad168ed8f8caacf46ba3da65a0db9adcba70f346be4781fc3b950c6e53fd981bcec4ee3a7a8b0d0cf135477d7a14ae2cb6b | v=spf1 ip4:54.208.176.96/32 include:_spf.google.com include:sendgrid.net include:_spf.salesforce.com include:mail.zendesk.com include:3853670.spf10.hubspotemail.net ~all | vmware-cloud-verification-3432f034-4f58-4f8b-b600-5b4e0a589608 |
| TXT | _dmarc.mparticle.com | v=DMARC1; p=quarantine; sp=quarantine; fo=1; ruf=mailto:rokt-t@dmarc.report-uri.com; rua=mailto:rokt-t@dmarc.report-uri.com; |
| CAA | mparticle.com | 0 iodef "mailto:security@mparticle.com" | 0 issue "amazon.com" | 0 issue "digicert.com" | 0 issue "globalsign.com" | 0 issue "godaddy.com" | 0 issue "letsencrypt.org" | 0 issuewild "globalsign.com" | 0 issuewild "godaddy.com" | 0 issuewild "letsencrypt.org" |
| DS | mparticle.com | — |