SurfaceMap › p › politeia.be

politeia.be

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

Domain & DNS

fail

20 passed 3 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    Zone transfer allowed
    Nameservers · These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: ns2.1ago.be (168.119.232.205): 136 records; ns2.1ago.be (2a01:4f8:c2c:7303::1): 136 records; ns2.politeia.be (168.119.232.205): 136 records; ns2.politeia.be (2a01:4f8:c2c:7303::1): 136 records. Restrict zone transfers to your secondary servers.
    #18
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns1.1ago.be, ns2.1ago.be; only in the zone: ns1.politeia.be, ns2.politeia.be. ns1.1ago.be, ns1.politeia.be, ns2.1ago.be, ns2.politeia.be report NS ns1.politeia.be ns2.politeia.be.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns2.1ago.be: "9.16.23-RH"; ns2.politeia.be: "9.16.23-RH". Hide or replace the version string.
    #17
  • !
    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 politeia.be ›

Mail

fail

19 passed 5 warn 2 failed

Areas

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

Problems

  • ✗
    13 DNS lookups, over the limit of 10
    SPF · SPF record needs 13 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.
    #2
  • ✗
    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
  • !
    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
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: k1 (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 politeia.be ›