wmata.com

Checked 22 October 2026, 11:32 UTC · via 8.8.8.8
✗Problems found
23 passed 4 warnings 1 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:170.121.14.15 ip4:170.121.14.25 ip4:170.121.14.23 ip4:170.121.14.24 ip4:72.28.124.142 ip4:72.28.124.143 ip4:52.167.222.166 ip4:52.168.149.8 ip4:52.159.95.174 include:rnmk.com include:spf_c.oraclecloud.com include:spf.protection.outlook.com -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.wmata.com)

Found

Record
v=DMARC1; p=none; rua=mailto:dmarc_agg@valigov.email,mailto:dmarc_agg@vali.email
Found at
_dmarc.wmata.com
External report address
mailto:dmarc_agg@valigov.email (authorized)
External report address
mailto:dmarc_agg@vali.email (authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:dmarc_agg@valigov.email,mailto:dmarc_agg@vali.emailAggregate report addresses

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_agg@valigov.email, mailto:dmarc_agg@vali.email
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: selector2

Found

Selectors
selector2
_domainkey
NOERROR
SelectorKeyFlags
selector2RSA 1024 bits

Checks

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

Signed, but no DS at parent

Found

DNSKEY records
Yes (2)
DS at parent
No
Algorithms
ECDSAP256SHA256 (13)
Key tags
2371, 34505
Signatures valid until
19 December 2026, 17:35 UTC

Checks

  • !
    Signed, but no DS at parent
    The zone is signed (DNSKEY present) but the parent has no DS record, so the chain of trust is incomplete. Publish the DS record at your registrar.
    #8
  • ✓ Signatures valid until 2026-12-19 #21
    DNSKEY signatures are valid until 2026-12-19T17:35:39Z.

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
0wmata-com.mail.protection.outlook.comA 52.101.8.68 A 52.101.41.58 A 52.101.194.155 A 52.101.60.154 AAAA 2a01:111:f403:c95d::a AAAA 2a01:111:f403:f908::8 AAAA 2a01:111:f403:f90d::1 AAAA 2a01:111:f403:f909::bmail-dm5pr05cu00104.inbound.protection.outlook.com ✓ mail-sj0pr02cu00102.inbound.protection.outlook.com ✓ mail-chtpr21cu00103.inbound.protection.outlook.com ✓ mail-bn0pr03cu00302.inbound.protection.outlook.com ✓ mail-ph5pr04cu00102.inbound.protection.outlook.com ✓ mail-bnypr05cu00100.inbound.protection.outlook.com ✓ mail-sn1pr0501cu00301.inbound.protection.outlook.com ✓ mail-bnypr03cu00203.inbound.protection.outlook.com ✓

Checks

  • ✓ 1 MX record #9
    Found 1 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.
  • !
    Single MX host, no backup
    Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • ✓ At most 5 MX records #13
    Found 1 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 8 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
wmata-com.mail.protection.outlook.comnone-

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