SurfaceMap › u › uhasselt.be

uhasselt.be

Checked 2026-10-22 07:20 UTC · first added 2026-10-21
!Passed with warnings Score 76 of 100

Domain & DNS

warn

22 passed 3 warn 0 failed

Areas

iRegistration !Delegation iNameservers ✓SOA !DNSSEC ✓Records

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. dns.uhasselt.be report NS dns.uhasselt.be dns.uhasselt.be dns.uhasselt.be dns.uhasselt.be dns.uhasselt.be dns.uhasselt.be dns.uhasselt.be dns.uhasselt.be dns.uhasselt.be dns.uhasselt.be dns.uhasselt.be dns.uhasselt.be dns.uhasselt.be dns.uhasselt.be dns.uhasselt.be dns.uhasselt.be dns.uhasselt.be dns.uhasselt.be dns.uhasselt.be dns.uhasselt.be ns1.belnet.be ns1.belnet.be ns1.belnet.be ns1.belnet.be ns2.belnet.be ns2.belnet.be ns2.belnet.be ns2.belnet.be ns3.belnet.be ns3.belnet.be ns3.belnet.be ns3.belnet.be.
    #7
  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: dns.uhasselt.be (glue 193.190.13.1, zone 193.190.13.1, 2001:6a8:2100:503::2). Update the glue at your registrar.
    #8
  • !
    Not signed
    DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Recent checks

!

Full report

Domain & DNS report for uhasselt.be ›

Mail

warn

24 passed 5 warn 0 failed

Areas

✓SPF !DMARC !DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits), selector2 (1024 bits), google (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Not configured
    TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32

Recent checks

!

Full report

Mail report for uhasselt.be ›