Mail domain report: vivium.be

SPF

pass

SPF record published

Found

Record: v=spf1 include:pvgroup.be ip4:193.239.210.31 ip4:217.117.48.66 ~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.vivium.be)

Found

Record: v=DMARC1; p=reject; rua=mailto:aony01id@ag.eu.dmarcadvisor.com; ruf=mailto:aony01id@fr.eu.dmarcadvisor.com; sp=reject; fo=1;
Found at: _dmarc.vivium.be
External report address: mailto:aony01id@ag.eu.dmarcadvisor.com (authorized)
External report address: mailto:aony01id@fr.eu.dmarcadvisor.com (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
sp	reject	Subdomain policy
rua	mailto:aony01id@ag.eu.dmarcadvisor.com	Aggregate report addresses
ruf	mailto:aony01id@fr.eu.dmarcadvisor.com	Failure report addresses
fo	1	Failure 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:aony01id@ag.eu.dmarcadvisor.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: mail, selector1, selector2

Found

Selectors: mail, selector1, selector2
_domainkey: NOERROR

Selector	Key	Flags
mail	RSA 1024 bits
selector1	RSA 1024 bits
selector2	RSA 2048 bits

Checks

✓ Keys found: mail, selector1, selector2 #7

DKIM keys found for this domain with selectors: mail, selector1, selector2
!

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

Signed, DS published at parent

Found

DNSKEY records: Yes (3)
DS at parent: Yes
Algorithms: ECDSAP256SHA256 (13)
Key tags: 48553, 8875, 12196
Signatures valid until: 29 October 2026, 03:17 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 expire in 164h0m0s

DNSKEY signatures expire at 2026-10-29T03:17:45Z (in 164h0m0s). Check that re-signing works.

#21

MX

warn

2 mail servers

Found

Priority	Host	Records	Reverse DNS
0	smtp1.pvgroup.be	CNAME mx1.hc749-91.c3s2.iphmx.com A 68.232.156.103 A 68.232.152.184	esa2.hc749-91.c3s2.iphmx.com ✓ esa1.hc749-91.c3s2.iphmx.com ✓
0	smtp2.pvgroup.be	CNAME mx2.hc749-91.c3s2.iphmx.com A 68.232.156.103 A 68.232.152.184	esa2.hc749-91.c3s2.iphmx.com ✓ esa1.hc749-91.c3s2.iphmx.com ✓

Checks

✓ 2 MX records #9

Found 2 MX records for this domain.
✓ All hosts resolve #10

All MX records resolve to valid IP addresses.
!

Hosts without IPv6

The following MX hosts could not be resolved to IPv6 addresses: smtp1.pvgroup.be, smtp2.pvgroup.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.
!

Hosts are CNAMEs

MX records must point to a host name with A/AAAA records, not to a CNAME: smtp1.pvgroup.be -> mx1.hc749-91.c3s2.iphmx.com, smtp2.pvgroup.be -> mx2.hc749-91.c3s2.iphmx.com

#22
✓ Reverse DNS confirmed #30

All 4 MX addresss 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 host	TLSA	DNSSEC
smtp1.pvgroup.be	none	-
smtp2.pvgroup.be	none	-

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

warn

https://www.pvgroup.be/common/email-img/PV/vivium_tiny_ps.svg

Found

Record: v=BIMI1; l=https://www.pvgroup.be/common/email-img/PV/vivium_tiny_ps.svg; a=;
Found at: default._bimi.vivium.be
Logo: https://www.pvgroup.be/common/email-img/PV/vivium_tiny_ps.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.