Digital exposure report
sofi.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://sofi.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 sofi.com
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- sofi.com
- Website request
- GET https://sofi.com/ → https://www.sofi.com/
- Scan time
- 2026-11-20 07:34:32 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 | 22/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.MediumCSP — protection from script injection · Hardening gap+8
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. 2 of 10 DNS lookups.
v=spf1 +mx include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all$ dig +short TXT sofi.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.sofi.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, s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
google._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCaZRfft8bwl/MFZjolml9uaMCB+69QI3nZ… s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAotAe4x4qWq4LhHlW0bCEhg0VPaGFjShs… s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDNjTys7kMt2oDTjdCX+tHb4KdZ+pAANQt+vxEp…
$ dig +short TXT google._domainkey.sofi.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-003a4d01.gslb.pphosted.com 10 mxb-003a4d01.gslb.pphosted.com
$ dig +short MX sofi.com
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://sofi.com/ returned HTTP 403 (final URL: https://www.sofi.com/). Client-side certificate validation passed.
HTTP 403 Final URL: https://www.sofi.com/
$ curl -sIL https://sofi.com/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://sofi.com/
HTTP 301 Location: https://sofi.com/
$ curl -sI http://sofi.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: Amazon Trust Services, expiring 2027-05-12 (173 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: Amazon Trust Services Valid from: 2026-10-27 Valid until: 2027-05-12 Names: *.mail.sofi.com, *.sofi.com, *.svc.sofi.com, sofi.com Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect sofi.com:443 -servername sofi.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://sofi.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://sofi.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://sofi.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://sofi.com/ | grep -i "X-Content-Type-Options"
Referrer-Policy
Passed · Severity: OK · 3/3Internal URLs don't leak to external sites.
Referrer-Policy: same-origin
Referrer-Policy: same-origin
$ curl -sIL https://sofi.com/ | grep -i "Referrer-Policy"
Permissions-Policy
Passed · Severity: OK · 2/2The site restricts access to sensitive browser features.
Permissions-Policy: accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credential
Permissions-Policy: accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=*
$ curl -sIL https://sofi.com/ | grep -i "Permissions-Policy"
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://sofi.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 sofi.com: NODATA
$ dig +short DS sofi.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 sofi.com SOA delv sofi.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 "globalsign.com" | 0 issue "godaddy.com" | 0 issue "letsencrypt.org" | 0 issue "pki.goog" | 0 issuewild "amazon.com" | 0 issuewild "globalsign.com" | 0 issuewild "godaddy.com" | 0 issuewild "pki.goog"
0 issue "amazon.com" 0 issue "globalsign.com" 0 issue "godaddy.com" 0 issue "letsencrypt.org" 0 issue "pki.goog" 0 issuewild "amazon.com" 0 issuewild "globalsign.com" 0 issuewild "godaddy.com" 0 issuewild "pki.goog"
$ dig +short CAA sofi.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.
george.ns.cloudflare.com marge.ns.cloudflare.com
$ dig +short NS sofi.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 | sofi.com | 104.18.38.31 | 172.64.149.225 |
| AAAA | sofi.com | — |
| MX | sofi.com | 10 mxa-003a4d01.gslb.pphosted.com | 10 mxb-003a4d01.gslb.pphosted.com |
| NS | sofi.com | george.ns.cloudflare.com | marge.ns.cloudflare.com |
| TXT | sofi.com | MS=ms72326802 | _ih4yod5o7l1kscwc50sk9oy050jdxs5 | apple-domain-verification=ouhb31SBg5PFvK7k | atlassian-domain-verification=Xu3U8fgrZvV7cVL3aObOTHZ4jAgYERrdVdotEZcSHb4GoXGUfFgrb9X+t1felzxw | docusign=86828977-0d4b-4c5a-9db4-64e25ab3421d | dropbox-domain-verification=ryxchpphz3fd | facebook-domain-verification=3ik6lghf0741hcq51f1j1pwvww3i9r | finicity_partner_id:2445582695895 | google-site-verification=463FQ-VU8mmpU42X6cV3B_XdKvoJ55BWyr4i8pyyI0A | google-site-verification=zV0MVDMvQbr7oB7izWsSqZcffe2U2OVWNSRIAPUZEME | jamf-site-verification=z2Zhng2HpOuyv1tBkWjA4g | mixpanel-domain-verify=c7b27301-d974-4974-93ff-95237ab5b591 | pardot_199992_*=a319bae9a2a05cbb5fb06421ff49e0d3d6c490dc056b66e21ed31ec36dbdacb8 | sending_domain1018022=0f9103734011234fe833fb99c9b5390311108b6a685db1dd026eb1baf5562352 | slack-domain-verification=je5Ma4ka8CYrgROIqIjjO8hS8GBxexskvHsNkAW8 | status-page-domain-verification=ptm1sdlyt8n4 | stripe-verification=318C532B7B249AF3760E8A7D4C9704D355690BE94574EC59E7411A30F8381332 | v=spf1 +mx include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all |
| TXT | _dmarc.sofi.com | v=DMARC1; p=reject; fo=1; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com; |
| CAA | sofi.com | 0 issue "amazon.com" | 0 issue "globalsign.com" | 0 issue "godaddy.com" | 0 issue "letsencrypt.org" | 0 issue "pki.goog" | 0 issuewild "amazon.com" | 0 issuewild "globalsign.com" | 0 issuewild "godaddy.com" | 0 issuewild "pki.goog" |
| DS | sofi.com | — |