Digital exposure report
snb.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.
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 snb.com
- 2.
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://snb.com/ | grep -i "Content-Security-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- snb.com
- Website request
- GET https://snb.com/ → https://www.websterbank.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 | 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.MediumDNSSEC — signed DNS records · Hardening gap+7
- 2.LowPermissions-Policy · Hardening gap+2
- 3.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. 7 of 10 DNS lookups.
v=spf1 ip4:198.252.191.93 ip4:198.252.191.94 ip4:12.175.11.50 ip4:12.175.11.51 ip4:204.95.150.215 ip4:166.73.92.60 ip4:166.73.92.61 ip4:166.73.92.63 ip4:50.58.9.15 ip4:208.66.22.33 include:spf.protection.outlook.com include:spf.cashedge.com include:spf-00103102.pphosted.com a:outbd-pstfx.customercenter.net include:spf_c.oraclecloud.com include:spf-0015fa02.pphosted.com include:es._spf.adp.com ~all
$ dig +short TXT snb.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.snb.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: s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqv3z/i9Nlg35RYuxcSUZGY3+IUVG4XDI… s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDPEgAgpdcjTTIaMzMVIOh+efKqgRsBqhFrR85K…
$ dig +short TXT s1._domainkey.snb.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-00103102.gslb.pphosted.com 10 mxb-00103102.gslb.pphosted.com
$ dig +short MX snb.com
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://snb.com/ returned HTTP 200 (final URL: https://www.websterbank.com/). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.websterbank.com/
$ curl -sIL https://snb.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.snb.com/
HTTP 301 Location: https://www.snb.com/
$ curl -sI http://snb.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-13 (174 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-10-27 Valid until: 2027-05-13 Names: go.snb.com, online.snb.com, payments.websteronline.com, public.websteronline.com, snb.com, statements.websteronline.com Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect snb.com:443 -servername snb.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://snb.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', a broad source (* / https: / data:) — weakens XSS protection.
Content-Security-Policy: default-src * 'unsafe-inline' 'unsafe-eval'; img-src * 'unsafe-inline' 'unsafe-eval' 'self' data: https:; report-uri /report-csp-violation
$ curl -sIL https://snb.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://snb.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://snb.com/ | grep -i "X-Content-Type-Options"
Referrer-Policy
Passed · Severity: OK · 3/3Internal URLs don't leak to external sites.
Referrer-Policy: strict-origin-when-cross-origin
Referrer-Policy: strict-origin-when-cross-origin
$ curl -sIL https://snb.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://snb.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: WP Engine
$ curl -sIL https://snb.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 snb.com: NODATA
$ dig +short DS snb.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 snb.com SOA delv snb.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:domainadmin@snb.com" | 0 issue "comodo.com" | 0 issue "digicert.com" | 0 issue "entrust.net" | 0 issue "letsencrypt.org"
0 iodef "mailto:domainadmin@snb.com" 0 issue "comodo.com" 0 issue "digicert.com" 0 issue "entrust.net" 0 issue "letsencrypt.org"
$ dig +short CAA snb.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-1141.awsdns-14.org ns-1810.awsdns-34.co.uk ns-56.awsdns-07.com ns-658.awsdns-18.net
$ dig +short NS snb.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 | snb.com | 141.193.213.20 |
| AAAA | snb.com | — |
| MX | snb.com | 10 mxa-00103102.gslb.pphosted.com | 10 mxb-00103102.gslb.pphosted.com |
| NS | snb.com | ns-1141.awsdns-14.org | ns-1810.awsdns-34.co.uk | ns-56.awsdns-07.com | ns-658.awsdns-18.net |
| TXT | snb.com | MS=ms58854719 | amazonses:C75JYrpsWZLhGy3JbEY+g3FzB9Add2kuq9VH3KWG7GU= | apple-domain-verification=uZuerpVxaXr0DBhi | atlassian-domain-verification=/saLvbJJ4mvsrYuiAJwqLdupQZoW0e1EALFWalH6Sf20iE2pbcGu0zjtm7rGypZH | docusign=dd5eb23d-a594-4232-a6fd-9d6f0035f1db | google-site-verification=mfu19f-OQWrkF3N1EzeYJK9J6_XEWcDO88QlO3-f35Y | v=spf1 ip4:198.252.191.93 ip4:198.252.191.94 ip4:12.175.11.50 ip4:12.175.11.51 ip4:204.95.150.215 ip4:166.73.92.60 ip4:166.73.92.61 ip4:166.73.92.63 ip4:50.58.9.15 ip4:208.66.22.33 include:spf.protection.outlook.com include:spf.cashedge.com include:spf-00103102.pphosted.com a:outbd-pstfx.customercenter.net include:spf_c.oraclecloud.com include:spf-0015fa02.pphosted.com include:es._spf.adp.com ~all |
| TXT | _dmarc.snb.com | v=DMARC1; p=reject; fo=1; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com |
| CAA | snb.com | 0 iodef "mailto:domainadmin@snb.com" | 0 issue "comodo.com" | 0 issue "digicert.com" | 0 issue "entrust.net" | 0 issue "letsencrypt.org" |
| DS | snb.com | — |