Mail domain report: vevioz.com

SPF

pass

SPF record published

Found

Record: v=spf1 include:_spf.google.com ip4:23.254.205.3 ~all
DNS lookups: 1 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
✓ 1 of 10 DNS lookups #2

SPF record needs 1 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.vevioz.com)

Found

Record: v=DMARC1; p=none; rua=mailto:001017419def429b9a5e359ea36e70bd@dmarc-reports.cloudflare.net
Found at: _dmarc.vevioz.com
External report address: mailto:001017419def429b9a5e359ea36e70bd@dmarc-reports.cloudflare.net (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
rua	mailto:001017419def429b9a5e359ea36e70bd@dmarc-reports.cloudflare.net	Aggregate report addresses

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:001017419def429b9a5e359ea36e70bd@dmarc-reports.cloudflare.net
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

DKIM

pass

Selectors: dkim

Found

Selectors: dkim
_domainkey: NOERROR

Selector	Key	Flags
dkim	RSA 2048 bits

Checks

✓ Keys found: dkim #7

DKIM keys found for this domain with selectors: dkim
✓ Strong keys #23

DKIM keys are strong enough: dkim: RSA 2048 bits.
✓ No problematic flags #24

No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

warn

Signed, but no DS at parent

Found

DNSKEY records: Yes (2)
DS at parent: No
Algorithms: ECDSAP256SHA256 (13)
Key tags: 34505, 2371
Signatures valid until: 29 November 2026, 06:37 UTC

Checks

!

Signed, but no DS at parent

The zone is signed (DNSKEY present) but the parent has no DS record, so the chain of trust is incomplete. Publish the DS record at your registrar.

#8
✓ Signatures valid until 2026-11-29 #21

DNSKEY signatures are valid until 2026-11-29T06:37:07Z.

MX

warn

1 mail server

Found

Priority	Host	Records	Reverse DNS
10	mail.vevioz.com	A 23.254.205.3	mail.vevioz.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.
!

Hosts without IPv6

The following MX hosts could not be resolved to IPv6 addresses: mail.vevioz.com

#11
!

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

TLS

fail

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

Found

MTA-STS record: v=STSv1; id=20240205;
Policy URL: https://mta-sts.vevioz.com/.well-known/mta-sts.txt
Mode: enforce
Allowed MX: aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, mail.vevioz.com
Max age: 604800 seconds
TLS-RPT record: v=TLSRPTv1; rua=mailto:postmaster@vevioz.com

DANE (TLSA records)

MX host	TLSA	DNSSEC
mail.vevioz.com	3 1 1 af102d931eb98a5e…	No

Checks

✓ Record published #32

MTA-STS record found with id 20240205.
✓ Policy enforced #33

The MTA-STS policy is enforced and cached for 168h0m0s.
✓ All MX hosts covered #34

Every MX host matches an mx: line of the MTA-STS policy.
✓ Reports enabled #35

TLS reports are sent to: mailto:postmaster@vevioz.com
✗

TLSA records not DNSSEC-validated

These MX hosts publish TLSA records that the resolver could not validate with DNSSEC, so senders ignore them or, if validation fails, may refuse delivery: mail.vevioz.com.

#36

BIMI

fail

https://assets.vevioz.com/bimi/bimi.svg

Found

Record: v=BIMI1; l=https://assets.vevioz.com/bimi/bimi.svg; avp=brand;
Found at: default._bimi.vevioz.com
Logo: https://assets.vevioz.com/bimi/bimi.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 not strict enough for BIMI

Mail clients will not show the logo. BIMI requires DMARC p=quarantine or p=reject (now p=none), a subdomain policy other than sp=none.

#39