SurfaceMap › u › usaintlouis.be

usaintlouis.be

Checked 2026-10-22 07:21 UTC · first added 2026-10-21
✗Problems found Score 66 of 100

Domain & DNS

warn

25 passed 3 warn 0 failed

Areas

iRegistration iDelegation iNameservers !SOA !DNSSEC iRecords

Problems

  • !
    Unusual SOA timers
    SOA · retry 2h should be shorter than refresh 2h. Current values: refresh 2h, retry 2h, expire 14d, negative TTL 1h.
    #23
  • !
    Signatures expire soon
    DNSSEC · The earliest signature expires at 2026-10-29 00:00 UTC (in 161h0m0s). Check that automatic re-signing works.
    #30
  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 1 iteration and a 4-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.
    #31

Recent checks

!

Full report

Domain & DNS report for usaintlouis.be ›

Mail

fail

22 passed 5 warn 1 failed

Areas

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

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    Signatures expire in 161h0m0s
    DNSSEC · DNSKEY signatures expire at 2026-10-29T00:00:00Z (in 161h0m0s). Check that re-signing works.
    #21
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Report address not authorized
    DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:rua-dmarc@uclouvain.be (needs usaintlouis.be._report._dmarc.uclouvain.be); mailto:ruf-dmarc@uclouvain.be (needs usaintlouis.be._report._dmarc.uclouvain.be). Ask the report provider to publish the record, or check the address.
    #29
  • !
    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 usaintlouis.be ›