SurfaceMap › p › parentia.be

parentia.be

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

Domain & DNS

fail

22 passed 2 warn 1 failed

Areas

iRegistration iDelegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns4.nrb.be (2a02:7100:0:301::101): read udp [2a01:4f8:1c1c:eebf::1]:34049->[2a02:7100:0:301::101]:53: i/o timeout.
    #14
  • !
    Invalid contact address
    SOA · The SOA RNAME "nobody.invalid" is not a valid mailbox (expected e.g. hostmaster.example.com).
    #25
  • !
    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 parentia.be ›

Mail

warn

25 passed 4 warn 0 failed

Areas

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

Problems

  • !
    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: k1 (1024 bits), selector1 (1024 bits), s1 (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 parentia.be ›