riotinto.com

Checked 22 October 2026, 10:31 UTC · via 8.8.8.8
!Passed with warnings
24 passed 5 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:203.15.191.188/32 ip4:203.15.191.189/32 ip4:203.15.191.252/32 ip4:203.15.191.253/32 ip4:203.15.190.226/32 ip4:203.15.190.227/32 ip4:208.185.229.0/24 ip4:208.185.235.0/24 ip4:148.59.108.0/23 ip4:148.59.106.0/23 ip4:148.59.107.25/32 ip4:148.59.109.25/32 ip4:182.160.163.188/32 ip4:157.133.127.52/32 ip4:205.236.155.25/32 ip4:69.20.6.34/32 ip4:87.253.233.6/32 ip4:3.226.40.151/32 ip4:159.183.181.113 ip4:149.72.116.19 ip4:149.72.117.225 ip4:149.72.119.192 ip4:149.72.119.197 ip4:149.72.119.199 ip4:149.72.119.210 ip4:149.72.147.106 ip4:149.72.148.50 ip4:149.72.155.21 ip4:149.72.160.121 ip4:149.72.166.148 ip4:35.80.141.6 ip4:44.229.121.55 ip4:74.179.243.94 ip4:172.214.67.207 ip4:4.236.81.254 ip4:148.59.100.16/28 include:spf.protection.outlook.com include:_spf01.mykronos.com include:spf.mandrillapp.com include:_spf.salesforce.com include:servers.mcsv.net include:spf1.fraedom.com include:spfa.mailendo.com include:spf1.workhuman.com include:spf-us.wfs.cloud ip4:159.135.229.88/32 ip4:159.135.237.231/32 ip4:207.134.161.197/32 ip4:20.5.80.155/32 ip4:20.5.82.25/32 ip4:74.201.88.25/32 ip4:12.239.120.27/32 ip4:195.200.255.124 ip4:20.53.141.40 ip4:20.11.185.19 -all
DNS lookups
10 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 10 of 10 DNS lookups #2
    SPF record needs 10 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.riotinto.com)

Found

Record
v=DMARC1; p=reject; fo=1; rua=mailto:dmarc@riotinto.com; ruf=mailto:dmarc@riotinto.com
Found at
_dmarc.riotinto.com
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:dmarc@riotinto.comAggregate report addresses
rufmailto:dmarc@riotinto.comFailure report addresses
fo1Failure reporting options

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:dmarc@riotinto.com
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: default, k1, selector1, selector2, s1, s2

Found

Selectors
default, k1, selector1, selector2, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
defaultRSA 2048 bits
k1RSA 1024 bits
selector1RSA 2048 bits
selector2RSA 1024 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

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

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

1 mail server

Found

PriorityHostRecordsReverse DNS
0riotinto-com.mail.protection.outlook.comA 52.101.41.26 A 52.101.9.84 A 52.101.202.150 A 52.101.9.90mail-sj0pr03cu01702.inbound.protection.outlook.com ✓ mail-mn0pr04cu00204.inbound.protection.outlook.com ✓ mail-ph6pr04cu00106.inbound.protection.outlook.com ✓ mail-bl3pr02cu00102.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.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: riotinto-com.mail.protection.outlook.com
    #11
  • !
    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 4 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
riotinto-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