lexisveille.fr security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

49risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

1High

3Medium

2Low

1Info

Collected 15 hours ago13.0sfrom cache

Certificate Transparency2
DNS resolution2
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs1
Registration
DNS posture3
Email authentication0
Certificate
Security headers3
Archived URLs
Analysis7

noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.

SPF and DKIM alone do not protect the From: address a person sees. Without DMARC, a spoofed message can pass SPF for some other domain and still display yours.
What to do
Publish `_dmarc.lexisveille.fr TXT "v=DMARC1; p=none; rua=mailto:dmarc@lexisveille.fr"`, review the reports, then move to p=quarantine and p=reject.
asset: lexisveille.fr
CSP is the main defence that limits what an injected script can do. Without it, any XSS bug is fully exploitable.
What to do
Start with a report-only policy, tighten it against the reports, then enforce.
asset: https://lexisveille.fr/
Nothing tells receiving mail servers which hosts may send as @lexisveille.fr, so anyone can. Even a domain that sends no mail should say so, or it becomes a free spoofing target.
What to do
Publish `v=spf1 -all` to state that this domain sends no mail.
asset: lexisveille.fr
Without clientTransferProhibited, a compromised registrar account can move the domain to another registrar in days, with no second step.
What to do
Enable the transfer lock (and registrar lock, if offered) in the registrar control panel.
asset: lexisveille.fr
Full URLs — including any tokens or IDs in them — are sent to every third party the page links to.
What to do
Send `Referrer-Policy: strict-origin-when-cross-origin`.
asset: https://lexisveille.fr/
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: lexisveille.fr
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: lexisveille.fr

final https://lexisveille.fr/status 200time 3880msstack cloudflare · Drupal 10 (https://www.drupal.org)

–http:// redirects to https://port 80 did not answer
✓Strict-Transport-Security
max-age=31536000; includeSubDomains
✗Content-Security-Policy
✓Clickjacking protection
SAMEORIGIN, SAMEORIGIN
✓X-Content-Type-Options
nosniff, nosniff
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

–No MX records — domain does not receive mail
✗SPF
no record
✗DMARC
no record
–MTA-STSn/a

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓3 nameservers
ns1.reedelsevier.com ns2.reedelsevier.com ns3.reedelsevier.com

✓Registered with MARKMONITOR Inc.6.3 years old
lexisveille.fr
✓Registration expiry267 days
2027-06-01
✗Transfer lock
client update prohibited
✓3 nameservers at registry
ns1.reedelsevier.com ns2.reedelsevier.com ns3.reedelsevier.com

Address	Ports	CVEs	Edge	Network
86.65.42.36 lexisveille.fr +2	443	0	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

lexisveille.fr security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames