Mail domain report: recordedfuture.com

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:54.69.47.25/32 ip4:52.26.10.143/32 ip4:52.38.97.38/32 ip4:34.145.233.0/32 include:spf1.recordedfuture.com include:_spf.google.com include:252628.spf04.hubspotemail.net -all
DNS lookups: 8 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
✓ 8 of 10 DNS lookups #2

SPF record needs 8 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

pass

p=reject (_dmarc.recordedfuture.com)

Found

Record: v=DMARC1; p=reject; rua=mailto:rgxmw8tw@ag.dmarcian.com; pct=100;
Found at: _dmarc.recordedfuture.com
External report address: mailto:rgxmw8tw@ag.dmarcian.com (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
pct	100	Percentage of mail the policy applies to
rua	mailto:rgxmw8tw@ag.dmarcian.com	Aggregate report addresses

Checks

✓ Policy: reject #4

DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
✓ 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:rgxmw8tw@ag.dmarcian.com
✓ Subdomain policy: reject #20

Subdomains are covered by policy 'reject'.
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: google, s1, s2

Found

Selectors: google, s1, s2
_domainkey: NOERROR

Selector	Key	Flags
google	RSA 1024 bits
s1	RSA 2048 bits
s2	RSA 1024 bits

Checks

✓ Keys found: google, s1, s2 #7

DKIM keys found for this domain with selectors: google, s1, s2
!

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: google (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: 34505, 2371
Signatures valid until: 13 December 2026, 10:47 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-12-13 #21

DNSKEY signatures are valid until 2026-12-13T10:47:23Z.

MX

warn

3 mail servers

Found

Priority	Host	Records	Reverse DNS
5	mailstream-central.mxrecord.mx	A 172.65.64.78	no PTR
10	mailstream-east.mxrecord.io	A 172.65.213.128	no PTR
10	mailstream-west.mxrecord.io	A 172.65.220.210	no PTR

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: mailstream-central.mxrecord.mx, mailstream-east.mxrecord.io, mailstream-west.mxrecord.io

#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.
!

Addresses without reverse DNS

These MX addresses have no PTR record, which many receivers treat as a spam signal: 172.65.64.78 (mailstream-central.mxrecord.mx), 172.65.213.128 (mailstream-east.mxrecord.io), 172.65.220.210 (mailstream-west.mxrecord.io). Ask your hosting provider to set one.

#30

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
mailstream-central.mxrecord.mx	none	-
mailstream-east.mxrecord.io	none	-
mailstream-west.mxrecord.io	none	-

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

warn

https://go.recordedfuture.com/hubfs/logos-2021/brand-logo-square-black.svg

Found

Record: v=BIMI1; l=https://go.recordedfuture.com/hubfs/logos-2021/brand-logo-square-black.svg;
Found at: default._bimi.recordedfuture.com
Logo: https://go.recordedfuture.com/hubfs/logos-2021/brand-logo-square-black.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.