SurfaceMap › i › initiativecitoyenne.be

initiativecitoyenne.be

Checked 2026-10-22 06:40 UTC · first added 2026-10-21
✗Problems found Score 53 of 100

Domain & DNS

warn

19 passed 4 warn 0 failed

Areas

iRegistration !Delegation iNameservers !SOA !DNSSEC iRecords

Problems

  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 185.128.239.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Unusual SOA timers
    SOA · refresh 10m is outside 20m–1d. Current values: refresh 10m, retry 5m, expire 14d, negative TTL 5m.
    #23
  • !
    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 initiativecitoyenne.be ›

Mail

fail

17 passed 5 warn 2 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
  • ✗
    No DKIM keys published
    DKIM · _domainkey.initiativecitoyenne.be does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Ends with ?all (neutral)
    SPF · SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.
    #3
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    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
  • !
    Reverse DNS does not match
    MX · The PTR name of these addresses does not resolve back to the same address: 2001:4b98:dc4:8::217 -> spool8.mail.gandi.net, 2001:4b98:dc4:8::215 -> spool6.mail.gandi.net, 2001:4b98:dc4:8::216 -> spool7.mail.gandi.net.
    #30
  • !
    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 initiativecitoyenne.be ›