Digital exposure report
regions.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.
Tell browsers to always use the secure version
Helps browsers use HTTPS on future visits after they have received the policy.
Who can fix it: Your web host
How to verify after the fix
curl -sIL https://regions.com/ | grep -i "Strict-Transport-Security"
- 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://regions.com/ | grep -i "Content-Security-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- regions.com
- Website request
- GET https://regions.com/ → https://regions.com/personal-banking
- Scan time
- 2026-11-20 07:34:35 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 | 25/25 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | 0/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.HighHSTS — enforce encryption in the browser · Hardening gap+8
- 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. 1 of the 10 allowed DNS lookups.
v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com -all$ dig +short TXT regions.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.regions.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: default. Confirm signing with dkim=pass in a sent message's Authentication-Results.
default._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv6bwNXwV/NarNzSe1nthwwz7tkn6…
$ dig +short TXT default._domainkey.regions.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.
0 mx0a-002bc201.pphosted.com 0 mx0b-002bc201.pphosted.com 10 mxa-002bc201.gslb.pphosted.com 10 mxb-002bc201.gslb.pphosted.com
$ dig +short MX regions.com
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://regions.com/ returned HTTP 200 (final URL: https://regions.com/personal-banking). Client-side certificate validation passed.
HTTP 200 Final URL: https://regions.com/personal-banking
$ curl -sIL https://regions.com/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://regions.com/
HTTP 301 Location: https://regions.com/
$ curl -sI http://regions.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-04-10 (141 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-24 Valid until: 2027-04-10 Names: regions.com, www.regions.com Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect regions.com:443 -servername regions.com 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Failed · Severity: High · Hardening gap · 0/8Browsers aren't told to always use an encrypted connection, enabling interception attacks on public networks.
No Strict-Transport-Security header. Users are exposed to SSL stripping on the first request.
Strict-Transport-Security: (missing)
$ curl -sIL https://regions.com/ | grep -i "Strict-Transport-Security"
- Start with a short max-age (300 seconds) and make sure every subdomain works over HTTPS.
- Gradually raise it to 31536000 (one year) and add includeSubDomains.
- Consider preload only once the policy is stable — removal from the preload list is slow.
/* Strict-Transport-Security: max-age=31536000; includeSubDomains
Safety: This change is made in your server/CDN settings. Test on staging before production. HSTS is cached in the visitor's browser — a long max-age on a site without working HTTPS will block access.
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://regions.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://regions.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://regions.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://regions.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://regions.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://regions.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 regions.com: NODATA
$ dig +short DS regions.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 regions.com SOA delv regions.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:was@regions.com" | 0 issue "sectigo.com" | 0 issuewild ";"
0 iodef "mailto:was@regions.com" 0 issue "sectigo.com" 0 issuewild ";"
$ dig +short CAA regions.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.
ns0048.secondary.cloudflare.com ns0158.secondary.cloudflare.com
$ dig +short NS regions.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 diligence2 observed gaps
- SOC 2 / ISO 27001 baseline4 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 | regions.com | 45.60.241.200 |
| AAAA | regions.com | — |
| MX | regions.com | 0 mx0a-002bc201.pphosted.com | 0 mx0b-002bc201.pphosted.com | 10 mxa-002bc201.gslb.pphosted.com | 10 mxb-002bc201.gslb.pphosted.com |
| NS | regions.com | ns0048.secondary.cloudflare.com | ns0158.secondary.cloudflare.com |
| TXT | regions.com | 00D8W000004LQVu=1TBUy0000000Ayf | 00DVG000008Mz1p=1TBVG0000000QKH | 00DVG000009JV2y=1TBVG0000000SXN | 00DVG000009JVR7=1TBVG0000000SYz | Dynatrace-site-verification=076e1ef6-b7de-4d77-bd11-458852e277dd__24g4f86gr2234d7l42oncnukbk | Dynatrace-site-verification=50004836-543d-4b9b-868d-fba11ebd2903__30o361sal72pqd1k12nnmmjvaj | MS=ms50260122 | MS=ms95152811 | QCCSRDrOwY25u7R/Gz+KNCQbiDuWb/SPDhDR3YkweQ1p7UQXIf7qrMpezMN9YmOirtjHicKJ8F2G+Ol0mTHNaw== | _globalsign-domain-verification=EMRJXJmhXYMo-eQWVR_40CqkCGUtlntJAOeDx1q7xY | ahrefs-site-verification_6391d639fa27791584439aaef1da453ef99c1b73324727c9dac9b37ba44f7c58 | atlassian-domain-verification=wBV752DlpuE3UwyAbzWKxFPTntEcjutBPouGRK25x7hdg1KH/sm2AW6Y5gKgjWqC | axway-amplify=4ed1a031-6e54-4f2d-902a-bf81efdfbc6b | cisco-ci-domain-verification=4aa1a2b5c15dc379ab80516fd44ff38df6fb797f78584662a498f6b124ec3c52 | dell-technologies-domain-verification=regions.com_2f27ce81-ad3a-4f3d-92a7-eaa17f13f075_1792091322 | docusign=1997e80f-4f98-4e7c-948e-8a96e90a3603 | docusign=50d153f1-38a6-4af0-ae33-d0b91c3761d1 | globalsign-domain-verification=5fe568768e3f128edd1f9201cd18cb01 | google-gws-recovery-domain-verification=48064932 | google-site-verification=fqosSDCvuukIRbGgvQ9V2WpputZ3OLpq3M1D83VvKKY | google-site-verification=pCJg-KSPMEciLAhdjefmT4Yd06f_8I55ey4sYAf7DZo | h1-domain-verification=PEYHdnX9913SaSjWDkjBQh9XX1j1j7NNmjxi5yExn1CzqvqK | h3sfgksrnqx2kmr3slrj6vwscy7gqsny | hcp-domain-verification=f9812ae367c2356a4935ebd3cf38eef362edbf93a87d349b680012eea1fc77f3 | intacct-esk=351FD7E1F0638B3AE0635D06710ADFB1 | jamf-site-verification=9Qfhg3N5DWtMzOYln8HjWQ | jamf-site-verification=ex1_K5nIp_q9ambbD0jN2w | openai-domain-verification=dv-XfKLFLbF6rCRILTPhjUsYpCO | postman-domain-verification=f1710cb6f2ec65ef79f193d02fe4205cfc90415c7a3528bad49566131b3b8527b06381ec9e0f74e4f369f18c7f3cc429052c6bb11979d27372d32cb7f558f766 | smartsheet-site-validation=nNXozC8RejM6dUpKShPeGpe3Yyfn_lM6 | t0js80v2rbhztgwh9xzytwy6cng91jq1 | t2gl79j9pmks133ky99zw3mv5bdfx9mm | v=DKIM1:k=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB; | v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com -all | workplace-domain-verification=mZqQEyA8ILoFAp7rytebbKhx0lNFyi |
| TXT | _dmarc.regions.com | v=DMARC1; p=reject; fo=1; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com |
| CAA | regions.com | 0 iodef "mailto:was@regions.com" | 0 issue "sectigo.com" | 0 issuewild ";" |
| DS | regions.com | — |