tri.be

Checked 22 October 2026, 07:20 UTC · via 8.8.8.8
✗Problems found
20 passed 3 warnings 2 failed 2 info

SPF

warn

SPF record published

Found

Record
v=spf1 include:_spf.google.com include:servers.outfunnel.com include:mailgun.org ip4:142.93.20.24/32 ?all
DNS lookups
7 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 7 of 10 DNS lookups #2
    SPF record needs 7 DNS lookups (limit is 10).
  • !
    Ends with ?all (neutral)
    SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.
    #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

fail

No DMARC record found

Checks

  • ✗
    No DMARC record
    No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5

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

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

pass

5 mail servers

Found

PriorityHostRecordsReverse DNS
1aspmx.l.google.comA 142.251.127.26 AAAA 2a00:1450:4001:c21::1alcfrai-in-f26.1e100.net ✓ lcfrai-in-f26.1e100.net ✓
5alt1.aspmx.l.google.comA 142.250.147.26 AAAA 2a00:1450:4025:c01::1ard-in-f26.1e100.net ✓ rd-in-f26.1e100.net ✓
5alt2.aspmx.l.google.comA 172.253.152.26 AAAA 2a00:1450:4010:c22::1byulpptr-in-f26.1e100.net ✓ yulpptr-in-f27.1e100.net ✓
10alt3.aspmx.l.google.comA 192.179.20.26 AAAA 2404:6800:4000:1027::1ancboms-in-f26.1e100.net ✓ ncboms-in-f26.1e100.net ✓
10alt4.aspmx.l.google.comA 192.178.158.27 AAAA 2404:6800:4013:813::1alcdels-in-f27.1e100.net ✓ lcdels-in-f26.1e100.net ✓

Checks

  • ✓ 5 MX records #9
    Found 5 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 5 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 5 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 10 MX addresss have a PTR record that resolves back to them.

TLS

fail

MTA-STS record without policy · no TLS-RPT · DANE on 0 of 5 MX hosts

Found

MTA-STS record
v=STSv1; id=20251107
Policy URL
https://mta-sts.tri.be/.well-known/mta-sts.txt
Policy error
Get "https://mta-sts.tri.be/.well-known/mta-sts.txt": dial tcp: lookup mta-sts.tri.be on 127.0.0.53:53: no such host

DANE (TLSA records)

MX hostTLSADNSSEC
aspmx.l.google.comnone-
alt1.aspmx.l.google.comnone-
alt2.aspmx.l.google.comnone-
alt3.aspmx.l.google.comnone-
alt4.aspmx.l.google.comnone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 20251107.
  • ✗
    Policy not reachable
    The MTA-STS record exists but the policy could not be fetched, so senders ignore MTA-STS: Get "https://mta-sts.tri.be/.well-known/mta-sts.txt": dial tcp: lookup mta-sts.tri.be on 127.0.0.53:53: no such host.
    #33
  • !
    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
  • 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