triangle-factory.be

Checked 22 October 2026, 07:20 UTC · via 8.8.8.8
✗Problems found
25 passed 4 warnings 1 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:_custspf.one.com include:_spf.google.com include:mailgun.org ~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 #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.triangle-factory.be)

Found

Record
v=DMARC1;p=none ;pct=100;rua=mailto:dmarc@triangle-factory.be;ruf=mailto:dmarc@triangle-factory.be;rua=mailto:rua@dmarc.brevo.com;ri=86400;aspf=s;fo=1;
Found at
_dmarc.triangle-factory.be
External report address
mailto:rua@dmarc.brevo.com (authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
pct100Percentage of mail the policy applies to
ruamailto:rua@dmarc.brevo.comAggregate report addresses
rufmailto:dmarc@triangle-factory.beFailure report addresses
aspfsSPF alignment (r = relaxed, s = strict)
fo1Failure reporting options
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:rua@dmarc.brevo.com
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: mta, s1, s2

Found

Selectors
mta, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
mtaRSA 1024 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

  • ✓ Keys found: mta, s1, s2 #7
    DKIM keys found for this domain with selectors: mta, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: mta (1024 bits), s2 (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
11879, 65147
Signatures valid until
5 November 2026, 00: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-05 #21
    DNSKEY signatures are valid until 2026-11-05T00:00:00Z.

MX

warn

3 mail servers

Found

PriorityHostRecordsReverse DNS
10mx1.pub.mailpod8-cph3.one.comA 185.164.14.102mx1.pub.mailpod8-cph3.one.com ✓
10mx2.pub.mailpod8-cph3.one.comA 185.164.14.103mx2.pub.mailpod8-cph3.one.com ✓
10mx3.pub.mailpod8-cph3.one.comA 185.164.14.104mx3.pub.mailpod8-cph3.one.com ✓

Checks

  • ✓ 3 MX records #9
    Found 3 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: mx1.pub.mailpod8-cph3.one.com, mx2.pub.mailpod8-cph3.one.com, mx3.pub.mailpod8-cph3.one.com
    #11
  • ✓ Redundant MX hosts #12
    Found 3 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 3 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 3 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx1.pub.mailpod8-cph3.one.com3 1 1 e7531ab55e193541…Yes
mx2.pub.mailpod8-cph3.one.com3 1 1 e7531ab55e193541…Yes
mx3.pub.mailpod8-cph3.one.com3 1 1 e7531ab55e193541…Yes

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
  • !
    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 3 MX hosts 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