royalantwerpfc.be

Checked 22 October 2026, 07:10 UTC · via 8.8.8.8
!Passed with warnings
23 passed 4 warnings 0 failed 4 info

SPF

pass

SPF record published

Found

Record
v=spf1 -all
DNS lookups
0 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 0 of 10 DNS lookups #2
    SPF record needs 0 DNS lookups (limit is 10).
  • ✓ Ends with -all #3
    SPF record properly uses -all to restrict unauthorized senders.
  • ✓ 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.
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

pass

p=reject (_dmarc.royalantwerpfc.be)

Found

Record
v=DMARC1; p=reject; rua=mailto:0d1b87ce9747209@rep.dmarcanalyzer.com
Found at
_dmarc.royalantwerpfc.be
External report address
mailto:0d1b87ce9747209@rep.dmarcanalyzer.com (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:0d1b87ce9747209@rep.dmarcanalyzer.comAggregate report addresses

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.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:0d1b87ce9747209@rep.dmarcanalyzer.com
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

info

Selectors: default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2

Found

Selectors
default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
defaultrevoked
dkimrevoked
mailrevoked
emailrevoked
k1revoked
selector1revoked
selector2revoked
googlerevoked
zohorevoked
mxrevoked
keyrevoked
mtarevoked
pmrevoked
dkim-smtprevoked
s1revoked
s2revoked

Checks

  • ✓ Keys found: default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2 #7
    DKIM keys found for this domain with selectors: default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2
  • i
    All keys revoked
    All found keys are revoked (empty p=): default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2. That is fine if this domain no longer signs mail.
    #24

DNSSEC

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

warn

2 mail servers

Found

PriorityHostRecordsReverse DNS
10mx.acom.be(does not resolve)
20relay.acom.beA 109.68.161.128mx1.mail.tigron.net ✓

Checks

  • ✓ 2 MX records #9
    Found 2 MX records for this domain.
  • !
    Hosts without IP addresses
    The following MX hosts could not be resolved to IP addresses: mx.acom.be
    #10
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: mx.acom.be, relay.acom.be
    #11
  • ✓ Redundant MX hosts #12
    Found 2 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 2 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 1 MX address have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx.acom.benone-
relay.acom.benone-

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
  • i
    Not configured
    TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.
    #35
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #36

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