Digital exposure report
boursorama.com
Good shape, with a few gaps worth closing this quarter.
Scanned: 2026-11-21 09:50 UTC
Partial coverage: the score is based on 95% of applicable check weight. 1 unverified check(s) are excluded, not counted as failures.
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 boursorama.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://boursorama.com/ | grep -i "Referrer-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- boursorama.com
- Website request
- GET https://boursorama.com/ → https://www.boursorama.com/
- Scan time
- 2026-11-21 09:50:07 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- DKIM — digital signature on email · Not detected (common selectors only)
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 | 23/25 | 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.LowReferrer-Policy · Hardening gap+3
- 3.LowPermissions-Policy · Hardening gap+2
- 4.LowCSP — protection from script injection · Hardening gap+3
To verify
Couldn't be confirmed from public data, so excluded from the score. Checking them clarifies your posture; it doesn't guarantee a score change.
- DKIM — digital signature on email
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. 0 of the 10 allowed DNS lookups.
v=spf1 -all
$ dig +short TXT boursorama.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; aspf=s; sp=quarantine; ri=86400; rf=afrf; pct=100; rua=mailto:dmarc-rua@boursorama.fr,mailto:boursorama.rua@emailsecurity.merox.io; ruf=mailto:dmarc-ruf@boursorama.fr
$ dig +short TXT _dmarc.boursorama.com
DKIM — digital signature on email
Not detected (common selectors only) · Severity: OK · Not scoredNo DKIM key was found under the common selectors we probed. That doesn't mean DKIM is missing — selectors can't be listed from public DNS. Not scored.
A missing name for a probed selector (NXDOMAIN/NODATA) only means that selector isn't published. DKIM is marked unverified and excluded from the score. Check a sent message's Authentication-Results for dkim=pass and its s= selector.
Selectors checked: google, selector1, selector2, default, k1, s1, s2, dkim, mail, smtp — no key found google._domainkey: nxdomain selector1._domainkey: nxdomain selector2._domainkey: nxdomain default._domainkey: nxdomain k1._domainkey: nxdomain s1._domainkey: nxdomain s2._domainkey: nxdomain dkim._domainkey: nxdomain mail._domainkey: nxdomain smtp._domainkey: nxdomain
$ dig +short TXT google._domainkey.boursorama.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.
0 mx.boursorama.com
$ dig +short MX boursorama.com
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://boursorama.com/ returned HTTP 200 (final URL: https://www.boursorama.com/). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.boursorama.com/
$ curl -sIL https://boursorama.com/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://boursorama.com/
HTTP 301 Location: https://boursorama.com/
$ curl -sI http://boursorama.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: Let's Encrypt, expiring 2026-12-28 (36 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: Let's Encrypt Valid from: 2026-09-29 Valid until: 2026-12-28 Names: boursobank.com, boursorama-banque.com, boursorama.com Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect boursorama.com:443 -servername boursorama.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=16070400 (186 days), includeSubDomains, preload. ≥ 180 days recommended.
Strict-Transport-Security: max-age=16070400; includeSubDomains; preload
$ curl -sIL https://boursorama.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' *.boursorama.com *.boursobank.com
$ curl -sIL https://boursorama.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: DENY frame-ancestors 'self' *.boursorama.com *.boursobank.com
X-Frame-Options: DENY CSP frame-ancestors: 'self' *.boursorama.com *.boursobank.com
$ curl -sIL https://boursorama.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://boursorama.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://boursorama.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://boursorama.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://boursorama.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 boursorama.com: NODATA
$ dig +short DS boursorama.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 boursorama.com SOA delv boursorama.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 "infocert.it" | 0 issue "digicert.com" | 0 issue "letsencrypt.org"
0 issue "infocert.it" 0 issue "digicert.com" 0 issue "letsencrypt.org"
$ dig +short CAA boursorama.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.
6 NS servers.
a7-67.akam.net a14-67.akam.net a28-67.akam.net a6-67.akam.net a1-149.akam.net a13-67.akam.net
$ dig +short NS boursorama.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 rules1 unverified
- 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 | boursorama.com | 195.42.250.21 |
| AAAA | boursorama.com | — |
| MX | boursorama.com | 0 mx.boursorama.com |
| NS | boursorama.com | a7-67.akam.net | a14-67.akam.net | a28-67.akam.net | a6-67.akam.net | a1-149.akam.net | a13-67.akam.net |
| TXT | boursorama.com | 6zcg06ygzh309m915tcl37sl0s6g3fvx | 8HTWwegP1pgUcRHBD53lJDkBujSdZof06aTIa/sJP6YvTReDxeX1zegFDoSuONiV | 8c3aoiapfsb76qerrvbrhs9ir5 | 6qsgzj3k8dc6lz9scz009k7j4rv7z1st | evinh8n8f801fh60118t7k1vh3 | vxqbd2bdr02zkjszz03b926vs1b2bml2 | rl6g77fu4jv86qnunmdua03olu | _b9rdy55fabygo42g2p2kive860i5zwc | aV5rxgopBG5p1fWnUvt/K33knLrrH5115qnfsyrNklw= | 86q7o50q5ofeh0bjb0tgefcimj | v=spf1 -all | aV5rxgopBG5p1fWnUvt/K6D/86MYVQmxZYfIKbDG178= | google-site-verification=S37dHY2FFnXpnEENO0H3SaSlcjIGK_k23K4loR4D-dI | vhmngcbk8rld75csds6qua219t |
| TXT | _dmarc.boursorama.com | v=DMARC1; p=quarantine; aspf=s; sp=quarantine; ri=86400; rf=afrf; pct=100; rua=mailto:dmarc-rua@boursorama.fr,mailto:boursorama.rua@emailsecurity.merox.io; ruf=mailto:dmarc-ruf@boursorama.fr |
| CAA | boursorama.com | 0 issue "infocert.it" | 0 issue "digicert.com" | 0 issue "letsencrypt.org" |
| DS | boursorama.com | — |