libelle.be security report

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

53risk

Elevated

Several issues worth triaging this week.

0Critical

1High

3Medium

7Low

2Info

Collected 19 hours ago30.2sfrom cache

Certificate Transparency23
DNS resolution36
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs53
Registration
DNS posture3
Email authentication1
Certificate
Security headers0
Archived URLs
Analysis13

noteFound 23 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
noteFound 27 addresses; enriching the first 12.
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.
noteNo registration data: RDAP has no record at this level.
note4 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

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.libelle.be TXT "v=DMARC1; p=none; rua=mailto:dmarc@libelle.be"`, review the reports, then move to p=quarantine and p=reject.
asset: libelle.be
Without HSTS the browser will still try http:// first on a fresh visit, which is the window an on-path attacker uses.
What to do
Send `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you are sure everything works over HTTPS.
asset: https://www.libelle.be/
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://www.libelle.be/
No X-Frame-Options or CSP frame-ancestors directive, so another site can load this page invisibly inside its own and trick users into clicking.
What to do
Send `X-Frame-Options: DENY` or `Content-Security-Policy: frame-ancestors ’none’`.
asset: https://www.libelle.be/
bdimage.test.libelle.be appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: bdimage.test.libelle.be
bdimage.stage.libelle.be appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: bdimage.stage.libelle.be
www.email.test.libelle.be appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: www.email.test.libelle.be
www.email.stage.libelle.be appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: www.email.stage.libelle.be
Lets browsers guess content types, which turns some upload and text endpoints into script injection points.
What to do
Send `X-Content-Type-Options: nosniff` on every response.
asset: https://www.libelle.be/
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://www.libelle.be/
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: libelle.be
Mail to this domain can be downgraded to plaintext by an on-path attacker, because senders have no way to know TLS is required.
What to do
Publish an MTA-STS policy (a TXT record plus a small HTTPS-hosted file).
asset: libelle.be
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: libelle.be

final https://www.libelle.be/status 405time 16704msstack cloudflare

✓http:// redirects to https://
✗Strict-Transport-Security
✗Content-Security-Policy
✗Clickjacking protection
✗X-Content-Type-Options
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Receives mail via 1 server
libelle-be.mail.protection.outlook.com
✓SPFends in -all
v=spf1 mx ip4:91.212.185.178 ip4:91.212.185.176 ip4:37.58.40.58 ip4:37.58.40.61 ip4:158.127.0.0/16 a:relay.ix.combell-ops.net include:spf.protection.outlook.com include:spf.mandrillapp.com include:sanoma.ipggroup.eu include:spf.roularta.be -all
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓3 nameservers
ns1.european-server.eu ns3.european-server.com ns4.european-server.com

Address	Ports	Edge	Network
104.17.121.18 mail.libelle.be +3	80443205220532082208320862087+5	Cloudflare~	—
104.17.122.18 mail.libelle.be +2	80443205220532082208320862087+5	Cloudflare~	—
23.227.38.74 shop.libelle.be +4	80443205220532082208320862087+5	Cloudflare~	—
217.19.237.54 libelle.be +4	80443	direct	—
79.127.235.8 bdimage.test.libelle.be +11	80443	direct	—
79.127.235.6 bdimage.test.libelle.be +8	80443	direct	—
79.127.235.51 bdimage.test.libelle.be +6	80443	Cloudflare~	—
79.127.213.228 bdimage.test.libelle.be +3	80443	direct	—
13.224.245.50 s759.libelle.be +1	80	direct	—
13.224.245.111 s759.libelle.be +1	80	direct	—
13.224.245.119 s759.libelle.be +1	80	direct	—
13.224.245.7 s759.libelle.be +1	80	direct	—

Archived URLs

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

libelle.be security report

Elevated

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames