wpbrigade.com

Checked 22 October 2026, 11:33 UTC · via 8.8.8.8
✗Problems found
22 passed 5 warnings 2 failed 2 info

SPF

warn

SPF record published

Found

Record
v=spf1 mx include:spf.sendinblue.com include:netblocks.dreamhost.com include:relay.mailchannels.net include:loginpress.pro include:spf.protection.outlook.com -all
DNS lookups
8 of 10
Void lookups
0 of 2
Problem
include:loginpress.pro publishes 2 SPF records

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • !
    8 of 10 DNS lookups, with problems
    SPF record needs 8 DNS lookups (limit is 10). Problems found: include:loginpress.pro publishes 2 SPF records.
    #2
  • ✓ 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.wpbrigade.com)

Found

Record
v=DMARC1; p=none; sp=none; rua=mailto:dmarc@mailinblue.com!10m; ruf=mailto:dmarc@mailinblue.com!10m; rf=afrf; pct=100; ri=86400
Found at
_dmarc.wpbrigade.com
External report address
mailto:dmarc@mailinblue.com!10m (authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
spnoneSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:dmarc@mailinblue.com!10mAggregate report addresses
rufmailto:dmarc@mailinblue.com!10mFailure report addresses
rfafrfFailure report format
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@mailinblue.com!10m
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: mail, selector1, selector2

Found

Selectors
mail, selector1, selector2
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 1024 bits
selector1RSA 2048 bits
selector2RSA 2048 bits

Checks

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

2 mail servers

Found

PriorityHostRecordsReverse DNS
0mx1.mailchannels.netA 54.69.1.140ec2-54-69-1-140.us-west-2.compute.amazonaws.com ✓
0mx2.mailchannels.netA 54.187.177.89ec2-54-187-177-89.us-west-2.compute.amazonaws.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: mx1.mailchannels.net, mx2.mailchannels.net
    #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 2 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 2 MX hosts

Found

MTA-STS record
v=STSv1; id=20260117T1400
Policy URL
https://mta-sts.wpbrigade.com/.well-known/mta-sts.txt
Policy error
Get "https://mta-sts.wpbrigade.com/.well-known/mta-sts.txt": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-10-22T11:33:16Z is after 2025-09-03T09:38:25Z

DANE (TLSA records)

MX hostTLSADNSSEC
mx1.mailchannels.netnone-
mx2.mailchannels.netnone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 20260117T1400.
  • ✗
    Policy not reachable
    The MTA-STS record exists but the policy could not be fetched, so senders ignore MTA-STS: Get "https://mta-sts.wpbrigade.com/.well-known/mta-sts.txt": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-10-22T11:33:16Z is after 2025-09-03T09:38:25Z.
    #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