Back to results

Digital exposure report

uzgent.be

Good shape, with a few gaps worth closing this quarter.

Scanned: 2026-11-19 02:55 UTC

Full coverage: every applicable check was assessed.

B
80/100

What to do first

  1. 1.

    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://uzgent.be/ | grep -i "Content-Security-Policy"
  2. 2.

    Choose which companies may issue certificates for your domain

    This reduces the chance of a certificate being issued by a provider you did not choose.

    Who can fix it: Your domain registrar or DNS provider

    How to verify after the fix

    dig +short CAA uzgent.be

A starting point, not a security guarantee.

What this grade means

Tested hostname
uzgent.be
Website request
GET https://uzgent.be/
Scan time
2026-11-19 02:55:52 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 security28/30Spoofing email from this domain is hard.
Encryption & certificate25/25Traffic to the site is encrypted and the certificate is valid.
Browser protections17/30Some browser protections are missing.
DNS infrastructure10/15The domain's infrastructure works, but recommended hardening is missing.

Fix priorities

  1. 1.MediumCSP — protection from script injection · Hardening gap+8
  2. 2.LowCAA — who may issue certificates · Hardening gap+5
  3. 3.LowReferrer-Policy · Hardening gap+3
  4. 4.LowPermissions-Policy · Hardening gap+2

Findings

SPF — who may send mail for the domain

Passed · Severity: OK · 10/10

An authorized sender list is defined and mail from other servers is rejected.

Valid SPF record with -all. 2 of the 10 allowed DNS lookups.

Source data: DNS TXT uzgent.be
v=spf1 mx a ip4:193.191.170.50 ip4:193.191.170.51 ip4:193.191.170.55 ip4:193.191.170.52 ip4:193.191.170.54 ip4:193.191.170.59 ip4:193.191.170.104 ip4:193.191.170.66 ip4:193.191.170.67 ip4:193.191.170.68 ip4:193.191.170.69  -all
$ dig +short TXT uzgent.be
Documentation: RFC 7208 — SPF (https://www.rfc-editor.org/rfc/rfc7208) · M3AAWG — Email Authentication Best Practices (https://www.m3aawg.org/sites/default/files/m3aawg-email-authentication-recommended-best-practices-09-2020.pdf)

DMARC — anti-spoofing policy

Passed · Severity: OK · 13/15

Forged email in the company's name is sent to the spam folder.

Policy p=quarantine. p=quarantine — consider moving to p=reject.

Source data: DNS TXT _dmarc.uzgent.be
v=DMARC1;p=quarantine;rua=mailto:dmarccontact@uzgent.be
$ dig +short TXT _dmarc.uzgent.be
Documentation: RFC 7489 — DMARC (https://www.rfc-editor.org/rfc/rfc7489) · dmarc.org — FAQ (https://dmarc.org/resources/frequently-asked-questions/)

DKIM — digital signature on email

Passed · Severity: OK · 5/5

A 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: s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.

Source data: DNS TXT <selector>._domainkey.uzgent.be
s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApuqs2tCz6gw/z5T6aTFNvOYpoA/xkcTh…
s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDZ98MGQxcTzWS+0v+L6DpAMpjxDwYHa1P/p69G…
$ dig +short TXT s1._domainkey.uzgent.be
Documentation: RFC 6376 — DKIM (https://www.rfc-editor.org/rfc/rfc6376) · M3AAWG — Email Authentication Best Practices (https://www.m3aawg.org/sites/default/files/m3aawg-email-authentication-recommended-best-practices-09-2020.pdf)

MX — inbound mail routing

Passed · Severity: OK · unscored

Mail 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.

Source data: DNS MX uzgent.be
10 mail9.uzgent.be
20 mail10.uzgent.be
$ dig +short MX uzgent.be
Documentation: RFC 7505 — Null MX (https://www.rfc-editor.org/rfc/rfc7505) · RFC 5321 §5.1 — Locating the target host (https://www.rfc-editor.org/rfc/rfc5321#section-5.1)

HTTPS available

Passed · Severity: OK · 10/10

The site loads over an encrypted connection.

https://uzgent.be/ returned HTTP 200 (final URL: https://uzgent.be/). Client-side certificate validation passed.

Source data: HTTPS GET https://uzgent.be/
HTTP 200
Final URL: https://uzgent.be/
$ curl -sIL https://uzgent.be/
Documentation: OWASP — Transport Layer Security Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html) · Mozilla — Server Side TLS (https://wiki.mozilla.org/Security/Server_Side_TLS)

HTTP → HTTPS redirect

Passed · Severity: OK · 7/7

Visitors arriving at an unencrypted address are automatically sent to the secure version.

HTTP 308 → https://uzgent.be/

Source data: HTTP GET http://uzgent.be/ (redirects not followed)
HTTP 308
Location: https://uzgent.be/
$ curl -sI http://uzgent.be/ | grep -iE "^(HTTP|location)"
Documentation: OWASP — Transport Layer Security Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html) · RFC 6797 — HSTS (https://www.rfc-editor.org/rfc/rfc6797)

SSL/TLS certificate validity

Passed · Severity: OK · 8/8

The certificate was accepted by a validating TLS client at scan time.

Live TLS handshake succeeded. No matching certificate details were available from CT logs; run the verify command to see the served certificate's dates.

Source data: Certificate Transparency logs (certspotter) for uzgent.be
Live TLS handshake: certificate accepted
The CT log service was unavailable at the time of the check
Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect uzgent.be:443 -servername uzgent.be 2>/dev/null | openssl x509 -noout -issuer -dates
Documentation: Certificate Transparency (https://certificate.transparency.dev/) · Let's Encrypt — Docs (https://letsencrypt.org/docs/) · Mozilla — Server Side TLS (https://wiki.mozilla.org/Security/Server_Side_TLS)

HSTS — enforce encryption in the browser

Passed · Severity: OK · 8/8

Browsers are told to always use an encrypted connection to the site.

max-age=63072000 (730 days), includeSubDomains, preload. ≥ 180 days recommended.

Source data: Response headers from https://uzgent.be/
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload, max-age=63072000;includeSubDomains
$ curl -sIL https://uzgent.be/ | grep -i "Strict-Transport-Security"
Documentation: MDN — Strict-Transport-Security (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Strict-Transport-Security) · RFC 6797 — HSTS (https://www.rfc-editor.org/rfc/rfc6797) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

CSP — protection from script injection

Failed · Severity: Medium · Hardening gap · 0/8

Missing Content-Security-Policy header: this removes one layer of protection against script injection.

No Content-Security-Policy header found.

Source data: Response headers from https://uzgent.be/
Content-Security-Policy: (missing)
$ curl -sIL https://uzgent.be/ | grep -i "Content-Security-Policy"
Fix recommendation (effort: Complex)
  1. First publish Content-Security-Policy-Report-Only — it blocks nothing, it only reports.
  2. Collect violations for a week or two and tune the policy to your legitimate sources.
  3. 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.

Documentation: MDN — Content Security Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP) · OWASP — CSP Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html)

Clickjacking protection

Passed · Severity: OK · 5/5

The site can't be embedded by foreign sites.

X-Frame-Options: SAMEORIGIN

Source data: Response headers from https://uzgent.be/
X-Frame-Options: SAMEORIGIN
$ curl -sIL https://uzgent.be/ | grep -i "X-Frame-Options"
Documentation: MDN — X-Frame-Options (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Frame-Options) · OWASP — Clickjacking Defense (https://cheatsheetseries.owasp.org/cheatsheets/Clickjacking_Defense_Cheat_Sheet.html)

X-Content-Type-Options

Passed · Severity: OK · 4/4

The browser won't guess file types in a way that could execute code.

nosniff is set.

Source data: Response headers from https://uzgent.be/
X-Content-Type-Options: nosniff
$ curl -sIL https://uzgent.be/ | grep -i "X-Content-Type-Options"
Documentation: MDN — X-Content-Type-Options (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Content-Type-Options) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Referrer-Policy

Failed · Severity: Low · Hardening gap · 0/3

Internal URLs (including parameters) may leak to external sites.

Referrer-Policy is missing; the browser will use its default.

Source data: Response headers from https://uzgent.be/
Referrer-Policy: (missing)
$ curl -sIL https://uzgent.be/ | grep -i "Referrer-Policy"
Fix recommendation (effort: Easy)
  1. 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.

Documentation: MDN — Referrer-Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Referrer-Policy) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Permissions-Policy

Needs attention · Severity: Low · Hardening gap · 0/2

Access to sensitive features like the camera and location isn't restricted.

Missing Permissions-Policy header.

Source data: Response headers from https://uzgent.be/
Permissions-Policy: (missing)
$ curl -sIL https://uzgent.be/ | grep -i "Permissions-Policy"
Fix recommendation (effort: Easy)
  1. 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.

Documentation: MDN — Permissions-Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Permissions-Policy) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Software version disclosure

Passed · Severity: OK · unscored

The server doesn't disclose software versions.

No version numbers found in the Server / X-Powered-By headers.

Source data: Response headers from https://uzgent.be/
server: cloudflare
x-powered-by: (missing)
$ curl -sIL https://uzgent.be/ | grep -iE "^(server|x-powered-by)"
Documentation: OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

DNSSEC — signed DNS records

Passed · Severity: OK · 7/7

The domain's records are digitally signed and hard to forge.

An AD (Authenticated Data) flag was returned by a validating resolver.

Source data: DNS-over-HTTPS (Cloudflare / Google): AD flag and DS record at the parent
AD = true
$ dig +dnssec uzgent.be | grep -E "flags:.* ad"
Documentation: RFC 4033 — DNSSEC (https://www.rfc-editor.org/rfc/rfc4033) · ICANN — DNSSEC: what and why (https://www.icann.org/resources/pages/dnssec-what-is-it-why-important-2019-03-05-en)

CAA — who may issue certificates

Needs attention · Severity: Low · Hardening gap · 0/5

Any certificate authority can issue a certificate for the domain, raising the risk of mis-issuance.

No CAA records found. RFC 8659 lets the domain owner restrict which CAs are authorized.

Source data: DNS CAA uzgent.be
(no CAA records found)
$ dig +short CAA uzgent.be
Fix recommendation (effort: Easy)
  1. Identify which certificate authority issued your current certificate (see the certificate check).
  2. Publish CAA for that authority only, and add iodef to receive alerts.
uzgent.be.  CAA  0 issue "letsencrypt.org"
uzgent.be.  CAA  0 iodef "mailto:security@uzgent.be"

Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. If your CDN issues certificates on your behalf, include it too — otherwise certificate renewal will fail.

Documentation: RFC 8659 — CAA (https://www.rfc-editor.org/rfc/rfc8659)

DNS server redundancy

Passed · Severity: OK · 3/3

The domain is served by several DNS servers, so one server failing won't take it down.

6 NS servers.

Source data: DNS NS uzgent.be
ns1.belnet.be
ns2.belnet.be
ns3.belnet.be
uzg11.uzgent.be
uzg22.uzgent.be
uzg44.uzgent.be
$ dig +short NS uzgent.be
Documentation: RFC 2182 — Secondary DNS server operation (https://www.rfc-editor.org/rfc/rfc2182)

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.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

Auzgent.be194.32.154.51
AAAAuzgent.be—
MXuzgent.be10 mail9.uzgent.be | 20 mail10.uzgent.be
NSuzgent.bens1.belnet.be | ns2.belnet.be | ns3.belnet.be | uzg11.uzgent.be | uzg22.uzgent.be | uzg44.uzgent.be
TXTuzgent.beMS=ms70534125 | ZOOM_verify_xeSCoPIYvNxSlNBBhPVxgk | apple-domain-verification=A1Zt0hWit7MvbdHV | Zs6GMa/gdncECn4HTOkB1qfsmwU7B1y/Qg1PEslLTIU= | google-gws-recovery-domain-verification=60435562 | facebook-domain-verification=iz968p0o68qgcgbv7qzqs0h5se1l2v | have-i-been-pwned-verification=dweb_cb36rp18usj94j823sqzrhdc | google-site-verification=GTFn1aVWB1G8NoDZYz9zFEb-cXK5_kY2wYOPmGUKWZk | google-site-verification=I3309ywUHGzWQcIYhS-xHsL6is1UaS2X8C78ZXLDxb8 | google-site-verification=TdcrjuOS-67pCUzAJ7IR5H_yBEGsHgqTcvbga0CArMg | google-site-verification=ThRulYIQgcE1SRkB0tb-MODuf_w0kNWnOZmrxlqTTes | rNy4UTXZfg91iFo8eQf9LIX5dbmzfbi2H/fBlimQuQXtb2SBOvXvtjZJRLPxx2xfWqbo1nfFcjCEhwYUVMurHg== | successfactors-site-verification=YjdjODY3N2M5YzdlZjBkZjMzYjdhZjI3ZmY1OGMyODc2MDU0NDViYjIwZmEzY2RlZjA5Y2QyNzhlZWY4ZWZmNg== | v=spf1 mx a ip4:193.191.170.50 ip4:193.191.170.51 ip4:193.191.170.55 ip4:193.191.170.52 ip4:193.191.170.54 ip4:193.191.170.59 ip4:193.191.170.104 ip4:193.191.170.66 ip4:193.191.170.67 ip4:193.191.170.68 ip4:193.191.170.69 -all
TXT_dmarc.uzgent.bev=DMARC1;p=quarantine;rua=mailto:dmarccontact@uzgent.be
CAAuzgent.be—
DSuzgent.be26959 8 2 aaa9bc28edf781e46412a7a723dd8e23bf2c6c66b2305acef3c38aea97b6db52 | 65124 8 2 a1494aba04246bc480b9bc548594569dcab8ac7274074114962f605cc1f8b52d
Passive check only: reading public DNS records, Certificate Transparency logs and ordinary GET requests to the homepage over HTTPS and HTTP. No changes were made to the scanned domain. Results are an indication and do not replace a professional security assessment.

Check your own domain