SurfaceMap › r › rcf.be

rcf.be

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

Domain & DNS

warn

26 passed 1 warn 0 failed

Areas

iRegistration iDelegation ✓Nameservers ✓SOA ✓DNSSEC !Records

Problems

  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), AAAA (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 1h; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for rcf.be ›

Mail

fail

23 passed 3 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
  • !
    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
  • !
    Unreadable DKIM key
    DKIM · These keys could not be parsed, so signatures made with them will fail: google (RSA public key could not be parsed).
    #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 rcf.be ›