nol-is.de

Checked 21 October 2026, 23:40 UTC · via 8.8.8.8
✗Problems found
28 passed 4 warnings 1 failed

SPF

pass

SPF record published

Found

Record
v=spf1 include:_spf.nol-is.de ~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

warn

p=quarantine (_dmarc.nol-is.de)

Found

Record
v=DMARC1; p=quarantine; rua=mailto:dmarc@nol-is.de; ruf=mailto:dmarc@nol-is.de; adkim=r; aspf=r; pct=100; fo=1; ri=604800
Found at
_dmarc.nol-is.de
TagValueMeaning
vDMARC1Version
pquarantinePolicy
pct100Percentage of mail the policy applies to
ruamailto:dmarc@nol-is.deAggregate report addresses
rufmailto:dmarc@nol-is.deFailure report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)
fo1Failure reporting options
ri604800Report interval (seconds)

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ 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:dmarc@nol-is.de
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NOERROR

Checks

  • !
    No key under common selectors
    The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (3)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
34680, 58432, 54448
Signatures valid until
4 November 2026, 13:19 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-04 #21
    DNSKEY signatures are valid until 2026-11-04T13:19:47Z.

MX

warn

2 mail servers

Found

PriorityHostRecordsReverse DNS
10mx01.nol-is.deA 85.114.145.139 AAAA 2001:4ba0:92e0:5139::1mail01.nol-is.de ✓ mail01.nol-is.de ✓
20mx00.nol-is.deA 80.82.223.84 AAAA 2001:4ba0:92f3:3:83::1nolis15.nol-is.de ✓ no PTR

Checks

  • ✓ 2 MX records #9
    Found 2 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.
  • ✓ 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.
  • !
    Addresses without reverse DNS
    These MX addresses have no PTR record, which many receivers treat as a spam signal: 2001:4ba0:92f3:3:83::1 (mx00.nol-is.de). Ask your hosting provider to set one.
    #30

TLS

fail

MTA-STS record without policy · TLS-RPT · DANE on 2 of 2 MX hosts

Found

MTA-STS record
v=STSv1; id=20181201000000Z
Policy URL
https://mta-sts.nol-is.de/.well-known/mta-sts.txt
Policy error
https://mta-sts.nol-is.de/.well-known/mta-sts.txt returned HTTP 403
TLS-RPT record
v=TLSRPTv1; rua=mailto:mta-sts@nol-is.de

DANE (TLSA records)

MX hostTLSADNSSEC
mx01.nol-is.de3 1 1 0a02e856cb1fe043… 3 1 1 83b46b77983ed6a8… 3 1 1 32baf2e5739eb60d… 3 1 1 cadac78061f4d91e…Yes
mx00.nol-is.de3 1 1 cadac78061f4d91e… 3 1 1 83b46b77983ed6a8… 3 1 1 32baf2e5739eb60d… 3 1 1 0a02e856cb1fe043…Yes

Checks

  • ✓ Record published #32
    MTA-STS record found with id 20181201000000Z.
  • ✗
    Policy not reachable
    The MTA-STS record exists but the policy could not be fetched, so senders ignore MTA-STS: https://mta-sts.nol-is.de/.well-known/mta-sts.txt returned HTTP 403.
    #33
  • ✓ Reports enabled #35
    TLS reports are sent to: mailto:mta-sts@nol-is.de
  • ✓ DANE on all MX hosts #36
    All 2 MX hosts publish DNSSEC-validated TLSA records.

BIMI

warn

https://bimi.nol-is.de/nol-is.de.svg

Found

Record
v=BIMI1; l=https://bimi.nol-is.de/nol-is.de.svg
Found at
default._bimi.nol-is.de
Logo
https://bimi.nol-is.de/nol-is.de.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.