liantis.be

Checked 22 October 2026, 06:42 UTC · via 8.8.8.8
✗Problems found
28 passed 4 warnings 1 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:194.78.38.27/32 ip4:194.78.38.2/32 ip4:185.111.57.5 include:spf.protection.outlook.com include:550275.spf04.hubspotemail.net include:spf.mandrillapp.com include:carerix.net include:mail.zendesk.com include:spf.topdesk.net include:spf.flexmail.eu include:sendgrid.net -all
DNS lookups
9 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1;p=reject;sp=reject;pct=100;rua=mailto:fko7acbf4x@rua.powerdmarc.com;ruf=mailto:fko7acbf4x@ruf.powerdmarc.com;adkim=r;aspf=s;fo=1:d:s;
Found at
_dmarc.liantis.be
External report address
mailto:fko7acbf4x@rua.powerdmarc.com (authorized)
External report address
mailto:fko7acbf4x@ruf.powerdmarc.com (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
sprejectSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:fko7acbf4x@rua.powerdmarc.comAggregate report addresses
rufmailto:fko7acbf4x@ruf.powerdmarc.comFailure report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfsSPF alignment (r = relaxed, s = strict)
fo1:d:sFailure reporting options

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:fko7acbf4x@rua.powerdmarc.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

warn

Selectors: selector1, s1, s2

Found

Selectors
selector1, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 1024 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

  • ✓ Keys found: selector1, s1, s2 #7
    DKIM keys found for this domain with selectors: selector1, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: selector1 (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
0liantis-be.mail.protection.outlook.comA 52.101.73.155 A 52.101.185.114 A 52.101.73.153 A 52.101.209.31 AAAA 2a01:111:f403:ca48::8 AAAA 2a01:111:f403:ca48::c AAAA 2a01:111:f403:ca04::d AAAA 2a01:111:f403:ca48::amail-am7pr02cu00203.inbound.protection.outlook.com ✓ mail-zrxpr04cu00102.inbound.protection.outlook.com ✓ mail-as8pr05cu00401.inbound.protection.outlook.com ✓ mail-cpjpr05cu00207.inbound.protection.outlook.com ✓ mail-miypr02cu00100.inbound.protection.outlook.com ✓ mail-miypr03cu00104.inbound.protection.outlook.com ✓ mail-db6pr03cu00105.inbound.protection.outlook.com ✓ mail-miypr02cu00202.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

fail

MTA-STS record without policy · TLS-RPT · DANE on 0 of 1 MX hosts

Found

MTA-STS record
v=STSv1; id=20230424162700
Policy URL
https://mta-sts.liantis.be/.well-known/mta-sts.txt
Policy error
Get "https://mta-sts.liantis.be/.well-known/mta-sts.txt": dial tcp: lookup mta-sts.liantis.be on 127.0.0.53:53: no such host
TLS-RPT record
v=TLSRPTv1; rua=mailto:fko7acbf4x@tls.powerdmarc.com

DANE (TLSA records)

MX hostTLSADNSSEC
liantis-be.mail.protection.outlook.comnone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 20230424162700.
  • ✗
    Policy not reachable
    The MTA-STS record exists but the policy could not be fetched, so senders ignore MTA-STS: Get "https://mta-sts.liantis.be/.well-known/mta-sts.txt": dial tcp: lookup mta-sts.liantis.be on 127.0.0.53:53: no such host.
    #33
  • ✓ Reports enabled #35
    TLS reports are sent to: mailto:fko7acbf4x@tls.powerdmarc.com
  • 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

warn

https://www.liantis.be/static/images/liantis.svg

Found

Record
v=BIMI1;l=https://www.liantis.be/static/images/liantis.svg
Found at
default._bimi.liantis.be
Logo
https://www.liantis.be/static/images/liantis.svg

Checks

  • !
    No certificate (a=)
    The logo is published without a Verified Mark Certificate. Gmail and Apple Mail only show BIMI logos with a VMC or CMC; Yahoo shows it without one.
    #38
  • ✓ DMARC meets BIMI requirements #39
    DMARC is enforced on all mail, as BIMI requires.