bbforum.be

Checked 22 October 2026, 06:10 UTC · via 8.8.8.8
✗Problems found
22 passed 5 warnings 1 failed 2 info

SPF

fail

SPF record published

Found

Record
v=spf1 a mx ip4:185.70.72.0/22 ip6:2a05:2880::/29
DNS lookups
2 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 2 of 10 DNS lookups #2
    SPF record needs 2 DNS lookups (limit is 10).
  • ✗
    No 'all' mechanism
    SPF record doesn't have an 'all' mechanism. Add -all or ~all at the end of your SPF record.
    #3
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✓ Single record #16
    Exactly one SPF record is published.
  • ✓ Valid syntax #25
    All SPF mechanisms and modifiers are valid.
  • ✓ No void lookups #26
    All include/redirect targets exist.
  • !
    Broad IP ranges
    These ranges authorize tens of thousands of addresses or more: ip6:2a05:2880::/29. Check that you really own and send from all of them.
    #27

DMARC

warn

p=reject (_dmarc.bbforum.be)

Found

Record
v=DMARC1; p=reject;
Found at
_dmarc.bbforum.be
TagValueMeaning
vDMARC1Version
prejectPolicy

Checks

  • ✓ Policy: reject #4
    DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • !
    No aggregate reports (rua)
    DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.

DKIM

info

DNS query for _domainkey.bbforum.be failed: read udp 46.225.38.91:32889->8.8.8.8:53: i/o timeout

Checks

  • i
    Could not be checked
    The DKIM lookup failed, so this could not be checked: DNS query for _domainkey.bbforum.be failed: read udp 46.225.38.91:32889->8.8.8.8:53: i/o timeout
    #7

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
ED25519 (15)
Key tags
48515, 55436
Signatures valid until
11 November 2026, 04:32 UTC

Checks

  • ✓ Signed, DS published at parent #8
    DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
  • ✓ Signatures valid until 2026-11-11 #21
    DNSKEY signatures are valid until 2026-11-11T04:32:35Z.

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
10mail1.futureweb.beA 185.70.72.81 AAAA 2a05:2880:0:20::1mail1.futureweb.be ✓ mail1.futureweb.be ✓

Checks

  • ✓ 1 MX record #9
    Found 1 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • ✓ All hosts have IPv6 #11
    All MX records resolve to IPv6 addresses.
  • !
    Single MX host, no backup
    Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • ✓ At most 5 MX records #13
    Found 1 MX records, which is within the recommended range (1-5).
  • ✓ No localhost targets #14
    No MX records pointing to localhost found.
  • ✓ No private IP addresses #15
    No MX records resolving to private IP addresses found.
  • ✓ No CNAME targets #22
    No MX records point to a CNAME.
  • ✓ Reverse DNS confirmed #30
    All 2 MX addresss have a PTR record that resolves back to them.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 1 of 1 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mail1.futureweb.be3 1 1 fdccdb7391bba164…Yes

Checks

  • !
    Not configured
    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
  • !
    Not configured
    MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".
    #35
  • ✓ DANE on all MX hosts #36
    All 1 MX host publish DNSSEC-validated TLSA records.

BIMI

info

No BIMI record

Checks

  • i
    Not configured
    BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.
    #38