vai.be

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

SPF

pass

SPF record published

Found

Record
v=spf1 a mx ip4:78.47.8.69 ip4:188.208.36.4 ip4:91.180.191.133 include:spf.protection.outlook.com include:servers.mcsv.net -all
DNS lookups
4 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 4 of 10 DNS lookups #2
    SPF record needs 4 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

fail

p=none (_dmarc.vai.be)

Found

Record
v=DMARC1; p=none; pct=100; rua=mailto:603899ed@in.mailhardener.com,mailto:dmarc@vai.be; fo=1
Found at
_dmarc.vai.be
External report address
mailto:603899ed@in.mailhardener.com (authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
pct100Percentage of mail the policy applies to
ruamailto:603899ed@in.mailhardener.com,mailto:dmarc@vai.beAggregate report addresses
fo1Failure reporting options

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:603899ed@in.mailhardener.com, mailto:dmarc@vai.be
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: k1, selector1, selector2, s1, s2

Found

Selectors
k1, selector1, selector2, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
k1RSA 1024 bits
selector1RSA 1024 bits
selector2RSA 1024 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

  • ✓ Keys found: k1, selector1, selector2, s1, s2 #7
    DKIM keys found for this domain with selectors: k1, selector1, selector2, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: k1 (1024 bits), selector1 (1024 bits), selector2 (1024 bits), s2 (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
10vai-be.mail.protection.outlook.comA 52.101.103.140 A 52.101.91.153 A 52.101.73.120 A 52.101.209.31 AAAA 2a01:111:f403:ca21::a AAAA 2a01:111:f403:ca48::c AAAA 2a01:111:f403:ca48::8 AAAA 2a01:111:f403:ca21::cmail-miypr02cu00204.inbound.protection.outlook.com ✓ mail-matpr04cu00101.inbound.protection.outlook.com ✓ mail-am7pr02cu00300.inbound.protection.outlook.com ✓ mail-cpjpr05cu00207.inbound.protection.outlook.com ✓ mail-maspr04cu00102.inbound.protection.outlook.com ✓ mail-miypr03cu00104.inbound.protection.outlook.com ✓ mail-miypr02cu00100.inbound.protection.outlook.com ✓ mail-matpr04cu00204.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
vai-be.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