Mail domain report: oanda.com

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:198.105.26.0/23 ip4:192.247.0.0/24 ip4:167.89.63.175 ip4:208.117.48.146 ip4:167.89.10.227 ip4:182.161.76.72 ip4:85.232.253.230 ip4:159.253.246.116 ip4:216.40.45.0/27 ip4:64.99.140.0/24 ip4:64.99.180.0/24 ip4:216.40.32.0/20 ip4:103.151.192.0/23 ip4:185.12.80.0/22 ip4:188.172.128.0/20 ip4:192.161.144.0/20 ip4:216.198.0.0/18 include:mktomail.com include:_spf.salesforce.com include:_spf.google.com include:spf.braintreegateway.com include:everbridge.net a:zgateway.zuora.com -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.oanda.com)

Found

Record: v=DMARC1; p=reject; rua=mailto:1f36a89dcc5e45da8794b48b6515fb79@dmarc-reports.cloudflare.net, mailto:dmarc@oanda.com, mailto:627ce0a5ef601@ag.dmarcly.com, mailto:dmarc_agg@dmarc.everest.email; ruf=mailto:1f36a89dcc5e45da8794b48b6515fb79@dmarc-reports.cloudflare.net, mailto:dmarc@oanda.com, mailto:627ce0a5ef601@ag.dmarcly.com; fo=1:d:s; pct=100; rf=afrf
Found at: _dmarc.oanda.com
External report address: mailto:1f36a89dcc5e45da8794b48b6515fb79@dmarc-reports.cloudflare.net (authorized)
External report address: mailto:627ce0a5ef601@ag.dmarcly.com (authorized)
External report address: mailto:dmarc_agg@dmarc.everest.email (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
pct	100	Percentage of mail the policy applies to
rua	mailto:1f36a89dcc5e45da8794b48b6515fb79@dmarc-reports.cloudflare.net, mailto:dmarc@oanda.com, mailto:627ce0a5ef601@ag.dmarcly.com, mailto:dmarc_agg@dmarc.everest.email	Aggregate report addresses
ruf	mailto:1f36a89dcc5e45da8794b48b6515fb79@dmarc-reports.cloudflare.net, mailto:dmarc@oanda.com, mailto:627ce0a5ef601@ag.dmarcly.com	Failure report addresses
fo	1:d:s	Failure reporting options
rf	afrf	Failure report format

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:1f36a89dcc5e45da8794b48b6515fb79@dmarc-reports.cloudflare.net, mailto:dmarc@oanda.com, mailto:627ce0a5ef601@ag.dmarcly.com, mailto:dmarc_agg@dmarc.everest.email
✓ 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: 2371, 34505
Signatures valid until: 20 December 2026, 23:25 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-20 #21

DNSKEY signatures are valid until 2026-12-20T23:25:01Z.

MX

pass

5 mail servers

Found

Priority	Host	Records	Reverse DNS
1	aspmx.l.google.com	A 142.251.127.27 AAAA 2a00:1450:4001:c21::1b	lcfrai-in-f27.1e100.net ✓ lcfrai-in-f27.1e100.net ✓
5	alt1.aspmx.l.google.com	A 142.250.147.27 AAAA 2a00:1450:4025:c01::1b	rd-in-f27.1e100.net ✓ rd-in-f27.1e100.net ✓
5	alt2.aspmx.l.google.com	A 172.253.152.27 AAAA 2a00:1450:4010:c22::1a	yulpptr-in-f27.1e100.net ✓ yulpptr-in-f26.1e100.net ✓
10	aspmx2.googlemail.com	A 142.250.147.26 AAAA 2a00:1450:4025:c01::1a	rd-in-f26.1e100.net ✓ rd-in-f26.1e100.net ✓
10	aspmx3.googlemail.com	A 172.253.152.27 AAAA 2a00:1450:4010:c22::1b	yulpptr-in-f27.1e100.net ✓ yulpptr-in-f27.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

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
aspmx.l.google.com	none	-
alt1.aspmx.l.google.com	none	-
alt2.aspmx.l.google.com	none	-
aspmx2.googlemail.com	none	-
aspmx3.googlemail.com	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

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