Digital exposure report
citizensbank.com
High exposure. Significant weaknesses put the brand, customers and email at risk.
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://citizensbank.com/ | grep -i "Content-Security-Policy"
- 2.
Send visitors to the secure version of your site
Visitors who type your address without https may stay on an unprotected connection.
Who can fix it: Your web host
How to verify after the fix
curl -sI http://citizensbank.com/ | grep -iE "^(HTTP|location)"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- citizensbank.com
- Website request
- GET https://citizensbank.com/
- Scan time
- 2026-11-20 07:34:50 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 | 30/30 | Spoofing email from this domain is hard. |
| Encryption & certificate | 18/25 | Encryption is in place, but a gap could expose users. |
| Browser protections | 7/30 | Several browser hardening headers are missing, which removes layers of protection against script injection and framing. |
| DNS infrastructure | 8/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.HighHTTP → HTTPS redirect · Hardening gap+7
- 2.MediumClickjacking protection · Hardening gap+5
- 3.MediumDNSSEC — signed DNS records · Hardening gap+7
- 4.MediumCSP — protection from script injection · Hardening gap+8
- 5.LowX-Content-Type-Options · Hardening gap+4
- 6.LowReferrer-Policy · Hardening gap+3
- 7.LowPermissions-Policy · Hardening gap+2
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 10/10An authorized sender list is defined and mail from other servers is rejected.
Valid SPF record with -all. 2 of the 10 allowed DNS lookups.
v=spf1 include:_cfgspf.citizensbank.com include:spf.protection.outlook.com -all
$ dig +short TXT citizensbank.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; sp=reject; fo=1; ri=3600; rua=mailto:citizens@rua.agari.com; ruf=mailto:citizens@ruf.agari.com
$ dig +short TXT _dmarc.citizensbank.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: selector1, selector2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
selector1._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAw+/g2Qlg1HbnHDbWtuoWXaMG3X5M… selector2._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA567zw9OizgQuVlg7pS+TvOl3IzBx…
$ dig +short TXT selector1._domainkey.citizensbank.com
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
1 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
10 citizensbank-com.mail.protection.outlook.com
$ dig +short MX citizensbank.com
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://citizensbank.com/ returned HTTP 403 (final URL: https://citizensbank.com/). Client-side certificate validation passed.
HTTP 403 Final URL: https://citizensbank.com/
$ curl -sIL https://citizensbank.com/
HTTP → HTTPS redirect
Failed · Severity: High · Hardening gap · 0/7The site is also reachable over an unencrypted connection, so data may travel in plain text on public networks.
http://citizensbank.com/ returned HTTP 403 without redirecting to https://.
HTTP 403 Location: (none)
$ curl -sI http://citizensbank.com/ | grep -iE "^(HTTP|location)"
- Set up a permanent (301) redirect from every HTTP request to HTTPS on the server or CDN.
- Then add an HSTS header.
server {
listen 80;
server_name citizensbank.com www.citizensbank.com;
return 301 https://$host$request_uri;
}Safety: This change is made on your server. Make sure HTTPS works first, otherwise the site won't load.
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-17 (117 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-08-31 Valid until: 2027-03-17 Names: citizensbank.com, citizensbanklive.com, citizenstools.com, citybeats.citizensbank.com, designsystem.citizensbank.com, madeready.com Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect citizensbank.com:443 -servername citizensbank.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=15768000 (183 days), no includeSubDomains. ≥ 180 days recommended.
Strict-Transport-Security: max-age=15768000
$ curl -sIL https://citizensbank.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://citizensbank.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
Failed · Severity: Medium · Hardening gap · 0/5Missing X-Frame-Options / frame-ancestors: this removes one layer of protection against clickjacking.
No valid X-Frame-Options and no frame-ancestors in the CSP.
X-Frame-Options: (missing)
$ curl -sIL https://citizensbank.com/ | grep -i "X-Frame-Options"
- Add X-Frame-Options: SAMEORIGIN (or DENY if the site is never embedded anywhere).
- Also set frame-ancestors in the CSP — the modern alternative.
/* X-Frame-Options: SAMEORIGIN
Safety: This change is made in your server/CDN settings. Test on staging before production. If partners embed the site in an iframe, add them to frame-ancestors instead of using DENY.
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://citizensbank.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://citizensbank.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://citizensbank.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://citizensbank.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 citizensbank.com: NODATA
$ dig +short DS citizensbank.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 citizensbank.com SOA delv citizensbank.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 "amazontrust.com" | 0 issue "sectigo.com" | 0 issue "pki.goog" | 0 issue "ssl.com" | 0 issue "digicert.com" | 0 issue "letsencrypt.org"
0 issue "amazontrust.com" 0 issue "sectigo.com" 0 issue "pki.goog" 0 issue "ssl.com" 0 issue "digicert.com" 0 issue "letsencrypt.org"
$ dig +short CAA citizensbank.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.
5 NS servers.
a22-67.akam.net a13-64.akam.net a20-66.akam.net a18-65.akam.net a1-203.akam.net
$ dig +short NS citizensbank.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.03 observed gaps
- NIS2 / vendor due diligence1 observed gaps
- SOC 2 / ISO 27001 baseline3 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 | citizensbank.com | 23.61.184.61 |
| AAAA | citizensbank.com | 2600:1407:3c00:1490::1f37 | 2600:1407:3c00:1488::1f37 |
| MX | citizensbank.com | 10 citizensbank-com.mail.protection.outlook.com |
| NS | citizensbank.com | a22-67.akam.net | a13-64.akam.net | a20-66.akam.net | a18-65.akam.net | a1-203.akam.net |
| TXT | citizensbank.com | ciscocidomainverification=358b903e04681980724b9a9d5b5600741d70cb34b8aff357220fceb4c5b06b31 | eA8gsC7ksaYBFA3Y9MdP1TtJzvpPMwQRlOQ4ciCtdu8nvrtZ8mPbgTnFeHZAfEbCKBoeh82XdE//rkAlwY8ryw== | smartsheet-site-validation=R6IFN1GzMMaLP1kyiuT51B6mOub1DVkJ | mongodb-site-verification=uLMSOsLxJor3iRZj5QwniJwNta0p3E6n | blitzy-domain-verification-krr54p=N17a8B42avtaNuNDReoSVnRXu | anthropic-domain-verification-bzq0h3=1oTLzuNoNueFJKQpGnqUn0UNS | google-site-verification=nB-dH36dKlMCOmilznloQMXVIuvyfZyHEWUFy_GZ4I4 | v=spf1 include:_cfgspf.citizensbank.com include:spf.protection.outlook.com -all | itV3w9jfX5YY0SVdyM+DOPRcoiSeAPsoX9Ha+/u0pgrzV6Lgjgzp1crDDshWftuOXYvlBEeUMiuQUtSRjOTi2A== | infoblox-domain-mastery=dd8193abfca36e933f6345cfc073171315e39ffb842653f6cca0f9e73215c90293 | df381782-7a09-42d5-b226-130161b16965 | Dynatrace-site-verification=f65bcae7-775d-4888-9f0e-d4b767589725__dtrj5lmuses9frcm7tfd08rfv8 | pardot1095902=5a2b2531a12e072803020b1bb1221c7ff762526dc63192668445054bfedd520c | onetrust-domain-verification=fc40aa7ca55743f9b37ce437e2f85bbe | openai-domain-verification=dv-FKW48gg3nLG7YYYpiRB76p03 | autodesk-domain-verification=fQ1TgpHzNuD-7n0qQdjI | kiro-site-verification=9076fafb-a6cd-49ca-9841-9104c2b4ddda | zoho-verification=zb64572473.zmverify.zoho.in | onetrust-domain-verification=7e0e9aa1e6d8417ca8cbd409530b6a89 | jamf-site-verification=2piiuQ0VZzuwD9aCheWIrA | postman-domain-verification=332213a0d1d8e5a694aad56646287cedbf6a287905b919862fe0c2c0d76c8c2292e16f894b713fbf602236794231acb689682a7c83140959739eabeebc084f92 | pardot641533=e064e5f20408674804d4883f54fb63c654d161ec1c7c8d7136a86440717acae6 | atlassian-domain-verification=0DHkQ/kHrdSAsQoLly7YEgz8v9KczaHPgu1mMHzkUCQJgXSUMWQe4gYk6Hd/gZP0 |
| TXT | _dmarc.citizensbank.com | v=DMARC1; p=reject; sp=reject; fo=1; ri=3600; rua=mailto:citizens@rua.agari.com; ruf=mailto:citizens@ruf.agari.com |
| CAA | citizensbank.com | 0 issue "amazontrust.com" | 0 issue "sectigo.com" | 0 issue "pki.goog" | 0 issue "ssl.com" | 0 issue "digicert.com" | 0 issue "letsencrypt.org" |
| DS | citizensbank.com | — |