velo-antwerpen.be

Checked 22 October 2026, 07:21 UTC · via 8.8.8.8
✗Problems found
19 passed 7 warnings 1 failed 3 info

SPF

warn

SPF record published

Found

Record
v=spf1 include:_u.velo-antwerpen.be._spf.smart.ondmarc.com ~all
DNS lookups
3 of 10
Void lookups
2 of 2
Problem
include:spf1.clearchannelint.com does not exist or has no records
Problem
include:spf2.clearchannelint.com does not exist or has no records

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • !
    3 of 10 DNS lookups, with problems
    SPF record needs 3 DNS lookups (limit is 10). Problems found: include:spf1.clearchannelint.com does not exist or has no records; include:spf2.clearchannelint.com does not exist or has no records.
    #2
  • ✓ 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.
  • !
    2 void lookups
    2 include/redirect targets does not exist or has no records (limit is 2). This usually is a stale include; remove it.
    #26
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

fail

p=none (_dmarc.velo-antwerpen.be)

Found

Record
v=DMARC1; p=none; pct=100; rua=mailto:dmarc.reports@clearchannelint.com; ruf=mailto:dmarc.forensics@clearchannel.be; rf=afrf;fo=1;adkim=r;aspf=s
Found at
_dmarc.velo-antwerpen.be
External report address
mailto:dmarc.reports@clearchannelint.com (not authorized)
External report address
mailto:dmarc.forensics@clearchannel.be (not authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
pct100Percentage of mail the policy applies to
ruamailto:dmarc.reports@clearchannelint.comAggregate report addresses
rufmailto:dmarc.forensics@clearchannel.beFailure report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfsSPF alignment (r = relaxed, s = strict)
fo1Failure reporting options
rfafrfFailure report format

Checks

  • ✗
    Policy: none (monitoring only)
    DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:dmarc.reports@clearchannelint.com
  • !
    Report address not authorized
    These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarc.reports@clearchannelint.com (needs velo-antwerpen.be._report._dmarc.clearchannelint.com); mailto:dmarc.forensics@clearchannel.be (needs velo-antwerpen.be._report._dmarc.clearchannel.be). Ask the report provider to publish the record, or check the address.
    #29

DKIM

warn

Selectors: mail, selector1

Found

Selectors
mail, selector1
_domainkey
NXDOMAIN
SelectorKeyFlags
mailRSA 1024 bits
selector1RSA 1024 bits

Checks

  • ✓ Keys found: mail, selector1 #7
    DKIM keys found for this domain with selectors: mail, selector1
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), selector1 (1024 bits). Rotate to a 2048-bit key.
    #23
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

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

1 mail server

Found

PriorityHostRecordsReverse DNS
0veloantwerpen-be01b.mail.protection.outlook.comA 52.101.99.2 A 52.101.89.1 A 52.101.89.2 A 52.101.89.18 AAAA 2a01:111:f403:ca0b::1 AAAA 2a01:111:f403:ca0b:: AAAA 2a01:111:f403:ca0b::6 AAAA 2a01:111:f403:ca1a::mail-cwxp265cu00502.inbound.protection.outlook.com ✓ mail-lo0p265cu00201.inbound.protection.outlook.com ✓ mail-lo3p265cu00302.inbound.protection.outlook.com ✓ mail-lo3p265cu00502.inbound.protection.outlook.com ✓ mail-lo3p265cu00301.inbound.protection.outlook.com ✓ mail-lo2p265cu02300.inbound.protection.outlook.com ✓ mail-lo3p265cu00506.inbound.protection.outlook.com ✓ mail-cwxp265cu00500.inbound.protection.outlook.com ✓

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 8 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
veloantwerpen-be01b.mail.protection.outlook.comnone-

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