atruvia.de

Checked 21 October 2026, 21:31 UTC · via 8.8.8.8
✗Problems found
21 passed 5 warnings 1 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 a:atruvia.de include:spf.fiduciagad.de include:spf.m-1.eu-1.quentn.com include:spf_c.oraclecloud.com include:spf.info-online.org ip4:54.229.2.165 ip4:52.30.130.201 -all
DNS lookups
10 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1;p=none;sp=none;pct=100;rua=mailto:dmarc-reports@atruvia.de;adkim=r;aspf=r;ri=86400
Found at
_dmarc.atruvia.de
TagValueMeaning
vDMARC1Version
pnonePolicy
spnoneSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:dmarc-reports@atruvia.deAggregate report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)
ri86400Report interval (seconds)

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:dmarc-reports@atruvia.de
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: default

Found

Selectors
default
_domainkey
NOERROR
SelectorKeyFlags
defaultRSA 1024 bits

Checks

  • ✓ Keys found: default #7
    DKIM keys found for this domain with selectors: default
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: default (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

8 mail servers

Found

PriorityHostRecordsReverse DNS
20gmail22.gadmail.deA 194.149.247.66gmail22.gadmail.de ✓
20gmail23.gadmail.deA 194.149.247.67gmail23.gadmail.de ✓
20omail22.gadmail.deA 195.200.34.243omail22.gadmail.de ✓
20omail23.gadmail.deA 195.200.34.245omail23.gadmail.de ✓
20rmail22.gadmail.deA 195.200.34.242rmail22.gadmail.de ✓
20rmail23.gadmail.deA 195.200.34.244rmail23.gadmail.de ✓
20wmail22.gadmail.deA 194.149.246.66wmail22.gadmail.de ✓
20wmail23.gadmail.deA 194.149.246.67wmail23.gadmail.de ✓

Checks

  • ✓ 8 MX records #9
    Found 8 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: gmail22.gadmail.de, gmail23.gadmail.de, omail22.gadmail.de, omail23.gadmail.de, rmail22.gadmail.de, rmail23.gadmail.de, wmail22.gadmail.de, wmail23.gadmail.de
    #11
  • ✓ Redundant MX hosts #12
    Found 8 MX records, which provides redundancy for email delivery.
  • !
    More than 5 MX records
    Found 8 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.
    #13
  • ✓ 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

no MTA-STS · no TLS-RPT · DANE on 0 of 8 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
gmail22.gadmail.denone-
gmail23.gadmail.denone-
omail22.gadmail.denone-
omail23.gadmail.denone-
rmail22.gadmail.denone-
rmail23.gadmail.denone-
wmail22.gadmail.denone-
wmail23.gadmail.denone-

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

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