dvgw.de

Checked 21 October 2026, 22:15 UTC · via 8.8.8.8
!Passed with warnings
29 passed 4 warnings 0 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 a mx ip4:195.227.0.82/32 ip4:13.93.49.118 ip4:23.97.146.145/32 ip4:20.238.218.208 ip4:20.103.42.117 ip4:13.81.10.189 a:web53.dvgw.cloud include:marketing.dynamics.com include:sendgrid.net include:spf.protection.outlook.com include:_spf.zimpel.de include:mail.uscreen.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

warn

p=reject (_dmarc.dvgw.de)

Found

Record
v=DMARC1; p=reject;
Found at
_dmarc.dvgw.de
TagValueMeaning
vDMARC1Version
prejectPolicy

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.
  • !
    No aggregate reports (rua)
    DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.

DKIM

warn

Selectors: selector1, s1, s2

Found

Selectors
selector1, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 1024 bits
s1RSA 2048 bits
s2RSA 2048 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). Rotate to a 2048-bit key.
    #23
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
38764, 3953
Signatures valid until
23 November 2026, 15:00 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 valid until 2026-11-23 #21
    DNSKEY signatures are valid until 2026-11-23T15:00:14Z.

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
0dvgw-de.y-v1.mx.microsoftA 52.101.73.145 A 52.101.68.25 A 52.101.103.162 A 52.101.209.28 AAAA 2a01:111:f403:ca09::24 AAAA 2a01:111:f403:ca48::8 AAAA 2a01:111:f403:ca09::a AAAA 2a01:111:f403:ca04::10mail-am6pr02cu00301.inbound.protection.outlook.com ✓ mail-db8pr02cu00101.inbound.protection.outlook.com ✓ mail-miypr03cu00202.inbound.protection.outlook.com ✓ mail-cpjpr05cu00104.inbound.protection.outlook.com ✓ mail-am6pr02cu00204.inbound.protection.outlook.com ✓ mail-miypr02cu00100.inbound.protection.outlook.com ✓ mail-am7pr02cu00202.inbound.protection.outlook.com ✓ mail-dbapr03cu00100.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

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

Found

MTA-STS record
v=STSv1; id=88979e91c1fcf828
Policy URL
https://mta-sts.dvgw.de/.well-known/mta-sts.txt
Mode
enforce
Allowed MX
dvgw-de.y-v1.mx.microsoft
Max age
604800 seconds

DANE (TLSA records)

MX hostTLSADNSSEC
dvgw-de.y-v1.mx.microsoft3 1 1 54883cc5f1849331… 2 0 1 ea7a25255d111fc3… 3 1 1 803f7447cc75b208… 2 0 1 c1ad7778796d20bc… 3 1 1 cfd68bde4129c00a…Yes

Checks

  • ✓ Record published #32
    MTA-STS record found with id 88979e91c1fcf828.
  • ✓ 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.
  • !
    Not configured
    MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".
    #35
  • ✓ DANE on all MX hosts #36
    All 1 MX host publish DNSSEC-validated TLSA records.

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