ionos.de

Checked 21 October 2026, 23:00 UTC · via 8.8.8.8
!Passed with warnings
29 passed 2 warnings 0 failed 3 info

SPF

info

SPF record published

Found

Record
v=spf1 redirect=_spf-corporate.ionos.com
DNS lookups
6 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 6 of 10 DNS lookups #2
    SPF record needs 6 DNS lookups (limit is 10).
  • i
    Delegated via redirect
    SPF record has no 'all' mechanism but redirects to _spf-corporate.ionos.com, whose policy applies.
    #3
  • ✓ 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.ionos.de)

Found

Record
v=DMARC1; p=reject; sp=reject; rua=mailto:sdwcwvtj@rua.eu.dmarcmanager.app; ri=86400; aspf=r; adkim=r
Found at
_dmarc.ionos.de
External report address
mailto:sdwcwvtj@rua.eu.dmarcmanager.app (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
sprejectSubdomain policy
ruamailto:sdwcwvtj@rua.eu.dmarcmanager.appAggregate report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)
ri86400Report interval (seconds)

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:sdwcwvtj@rua.eu.dmarcmanager.app
  • ✓ 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

pass

Selectors: google

Found

Selectors
google
_domainkey
NOERROR
SelectorKeyFlags
googleRSA 2048 bits

Checks

  • ✓ Keys found: google #7
    DKIM keys found for this domain with selectors: google
  • ✓ Strong keys #23
    DKIM keys are strong enough: google: RSA 2048 bits.
  • ✓ 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
RSASHA256 (8)
Key tags
15694, 50180
Signatures valid until
29 October 2026, 06:54 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-10-29 #21
    DNSKEY signatures are valid until 2026-10-29T06:54:13Z.

MX

warn

2 mail servers

Found

PriorityHostRecordsReverse DNS
10mxint01.1and1.comA 212.227.17.16 A 212.227.126.206mxint01.1and1.com ✓ mxint01.1and1.com ✓
10mxint02.1and1.comA 212.227.126.207 A 212.227.17.17mxint02.1and1.com ✓ mxint02.1and1.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: mxint01.1and1.com, mxint02.1and1.com
    #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.
  • ✓ No CNAME targets #22
    No MX records point to a CNAME.
  • ✓ 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 hostTLSADNSSEC
mxint01.1and1.comnone-
mxint02.1and1.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

pass

https://vmc.digicert.com/fcb79591-8667-4684-946b-0087b7b438cb.svg

Found

Record
v=BIMI1;l=https://vmc.digicert.com/fcb79591-8667-4684-946b-0087b7b438cb.svg;a=https://vmc.digicert.com/fcb79591-8667-4684-946b-0087b7b438cb.pem
Found at
default._bimi.ionos.de
Logo
https://vmc.digicert.com/fcb79591-8667-4684-946b-0087b7b438cb.svg
Certificate
https://vmc.digicert.com/fcb79591-8667-4684-946b-0087b7b438cb.pem

Checks

  • ✓ Logo and certificate published #38
    BIMI logo: https://vmc.digicert.com/fcb79591-8667-4684-946b-0087b7b438cb.svg; certificate: https://vmc.digicert.com/fcb79591-8667-4684-946b-0087b7b438cb.pem
  • ✓ DMARC meets BIMI requirements #39
    DMARC is enforced on all mail, as BIMI requires.