Digital exposure report
uzbrussel.be
Moderate exposure. There are gaps an attacker could exploit — fix them soon.
Scanned: 2026-11-20 07:30 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
Tell receiving mail servers how to treat fake email from your domain
Without this policy, inboxes have less guidance for spotting messages that impersonate you.
Who can fix it: Your email provider, together with whoever manages your DNS
How to verify after the fix
dig +short TXT _dmarc.uzbrussel.be
- 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://uzbrussel.be/ | grep -i "Content-Security-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- uzbrussel.be
- Website request
- GET https://uzbrussel.be/ → https://www.uzbrussel.be/
- Scan time
- 2026-11-20 07:30:29 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 | 19/30 | Spoofing email in the company's name is possible in some cases. |
| Encryption & certificate | 25/25 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | 20/30 | Some browser protections are missing. |
| DNS infrastructure | 8/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.MediumDMARC — anti-spoofing policy · Hardening gap+10
- 2.MediumDNSSEC — signed DNS records · Hardening gap+7
- 3.MediumCSP — protection from script injection · Hardening gap+8
- 4.LowPermissions-Policy · Hardening gap+2
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 9/10An authorized sender list is defined; mail from other servers is flagged as suspicious.
~all (softfail) — acceptable when combined with enforced DMARC. 5 of 10 DNS lookups.
v=spf1 a mx include:servers.mcsv.net include:spf.protection.outlook.com include:spf.flexmail.eu ip4:213.251.72.5 ip4:144.248.238.155 ~all
$ dig +short TXT uzbrussel.be
DMARC — anti-spoofing policy
Needs attention · Severity: Medium · Hardening gap · 5/15DMARC is in monitoring mode only — forged email still reaches recipients.
Policy p=none. p=none collects reports but does not protect.
v=DMARC1; p=none; rua=mailto:cesadmin@uzbrussel.be; ruf=mailto:cesadmin@uzbrussel.be
$ dig +short TXT _dmarc.uzbrussel.be
- Step 1 (monitoring, no effect on mail): publish p=none with an rua address to receive reports.
- Step 2: analyze reports for 2–4 weeks and make sure every legitimate sender passes SPF/DKIM.
- Step 3: move to p=quarantine, and finally to p=reject.
_dmarc.uzbrussel.be. TXT "v=DMARC1; p=none; rua=mailto:dmarc@uzbrussel.be; fo=1"
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. Jumping straight to reject without a monitoring phase can block legitimate mail.
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, k1, s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
selector1._domainkey: v=DKIM1; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAt6j6GaQj1c1VGjEnC3UzZs0XyjEc7LiFNSh… k1._domainkey: k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbNrX2cY/GUKIFx2G/1I00ftdAj713WP9AQ1xir85i8… s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA+NrsYJqTJqsODnLMKcH9gaPF7PD/12ga… s2._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwTj97x4GGb+F9ewkEiVICUpW48kjfmbo…
$ dig +short TXT selector1._domainkey.uzbrussel.be
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
2 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
10 smtp2.uzbrussel.be 10 smtp.uzbrussel.be
$ dig +short MX uzbrussel.be
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://uzbrussel.be/ returned HTTP 200 (final URL: https://www.uzbrussel.be/). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.uzbrussel.be/
$ curl -sIL https://uzbrussel.be/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://www.uzbrussel.be
HTTP 301 Location: https://www.uzbrussel.be
$ curl -sI http://uzbrussel.be/ | 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-27 (37 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-28 Valid until: 2026-12-27 Names: uzbrussel.be Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect uzbrussel.be:443 -servername uzbrussel.be 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=31536000 (365 days), includeSubDomains. ≥ 180 days recommended.
Strict-Transport-Security: max-age=31536000; includeSubDomains
$ curl -sIL https://uzbrussel.be/ | 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://uzbrussel.be/ | 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: SAMEORIGIN
X-Frame-Options: SAMEORIGIN
$ curl -sIL https://uzbrussel.be/ | 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://uzbrussel.be/ | grep -i "X-Content-Type-Options"
Referrer-Policy
Passed · Severity: OK · 3/3Internal URLs don't leak to external sites.
Referrer-Policy: strict-origin-when-cross-origin
Referrer-Policy: strict-origin-when-cross-origin
$ curl -sIL https://uzbrussel.be/ | grep -i "Referrer-Policy"
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://uzbrussel.be/ | 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://uzbrussel.be/ | 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 uzbrussel.be: NODATA
$ dig +short DS uzbrussel.be
- 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 uzbrussel.be SOA delv uzbrussel.be
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 "letsencrypt.org" | 0 issue "sectigo.com"
0 issue "letsencrypt.org" 0 issue "sectigo.com"
$ dig +short CAA uzbrussel.be
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
3 NS servers.
ns1.combell.eu ns4.combell.net ns3.combell.net
$ dig +short NS uzbrussel.be
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 observed gaps
- PCI DSS v4.01 observed gaps
- NIS2 / vendor due diligence2 observed gaps
- SOC 2 / ISO 27001 baseline2 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 | uzbrussel.be | 217.19.237.54 |
| AAAA | uzbrussel.be | — |
| MX | uzbrussel.be | 10 smtp2.uzbrussel.be | 10 smtp.uzbrussel.be |
| NS | uzbrussel.be | ns1.combell.eu | ns4.combell.net | ns3.combell.net |
| TXT | uzbrussel.be | spf2.0/pra include:spf.flexmail.eu ?all | google-site-verification=k0fnPJTpDiOnpa0WJL2Ky84j-7ZgOo5SOQVRouA6Gzc | facebook-domain-verification=5595w1f0we9p7wzbw6m3drlhwip1qt | apple-domain-verification=uY1CpCTL6DIa3pq3 | 87LHmtOFbK4xxFEeKgDuZzolCmOmEecWhdtZMlMM2TITozsEdwpzGn+D4+c3xkeMVouRp6cKtq5bFDRpLPHpXg== | atlassian-domain-verification=oJAbnuI0LWqT5IRfpSwBzqzbmXuk0GqcbIUSHu19ZupbeUtTGNqKrZ9MCaG3Eaaw | v=spf1 a mx include:servers.mcsv.net include:spf.protection.outlook.com include:spf.flexmail.eu ip4:213.251.72.5 ip4:144.248.238.155 ~all | MS=ms98484557 |
| TXT | _dmarc.uzbrussel.be | v=DMARC1; p=none; rua=mailto:cesadmin@uzbrussel.be; ruf=mailto:cesadmin@uzbrussel.be |
| CAA | uzbrussel.be | 0 issue "letsencrypt.org" | 0 issue "sectigo.com" |
| DS | uzbrussel.be | — |