rolls-royce.com

Checked 22 October 2026, 10:32 UTC · via 8.8.8.8
!Passed with warnings
23 passed 6 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 exists:%{i}.spf.rolls-royce.c3s2.iphmx.com ip4:132.244.72.69 ip4:132.244.72.54/31 ip4:192.40.173.140/31 ip4:46.235.193.39 ip4:46.235.193.40 ip4:62.13.153.174 ip4:192.73.18.10 ip4:185.79.166.10 ip4:185.227.62.134 ip4:193.42.254.24/31 ip4:185.4.4.17 ip4:54.229.2.165 ip4:52.30.130.201 ip4:85.159.248.144/28 ip4:143.55.147.19 ip4:66.159.244.74 ip4:212.127.3.148/30 ip4:212.127.1.148/30 ip4:64.95.144.128/25 ip4:64.94.2.0/28 ip4:128.136.242.224/27 ip4:45.15.193.192/27 ip4:139.178.74.40/29 ip4:66.159.228.13 ip4:66.159.227.13 include:spf.protection.outlook.com include:messagelabs.com include:u20095718.wl219.sendgrid.net include:spf.mailjet.com include:spfs.aravo.com ~all
DNS lookups
9 of 10
Void lookups
0 of 2

Checks

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

warn

p=quarantine (_dmarc.rolls-royce.com)

Found

Record
v=DMARC1; p=quarantine; rua=mailto:35a53a5e09d8012@rep.dmarcanalyzer.com; ruf=mailto:35a53a5e09d8012@for.dmarcanalyzer.com; pct=100; fo=1;
Found at
_dmarc.rolls-royce.com
External report address
mailto:35a53a5e09d8012@rep.dmarcanalyzer.com (authorized)
External report address
mailto:35a53a5e09d8012@for.dmarcanalyzer.com (authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
pct100Percentage of mail the policy applies to
ruamailto:35a53a5e09d8012@rep.dmarcanalyzer.comAggregate report addresses
rufmailto:35a53a5e09d8012@for.dmarcanalyzer.comFailure report addresses
fo1Failure reporting options

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ 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:35a53a5e09d8012@rep.dmarcanalyzer.com
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: dkim, pm, s1, s2

Found

Selectors
dkim, pm, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
dkimRSA 2048 bitstest mode (t=y), h=sha256
pmpublic key is not valid base64
s1RSA 2048 bits
s2RSA 1024 bits

Checks

  • ✓ Keys found: dkim, pm, s1, s2 #7
    DKIM keys found for this domain with selectors: dkim, pm, s1, s2
  • !
    Unreadable DKIM key
    These keys could not be parsed, so signatures made with them will fail: pm (public key is not valid base64).
    #23
  • !
    Key in test mode
    These keys have t=y, so receivers treat DKIM failures as a test: dkim. Remove t=y once DKIM works.
    #24

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

4 mail servers

Found

PriorityHostRecordsReverse DNS
10mxa-004f7902.gslb.pphosted.comA 66.159.244.74mx07-004f7902.pphosted.com ✓
10mxb-004f7902.gslb.pphosted.comA 143.55.147.19mx11-004f7902.pphosted.com ✓
20mx1.rolls-royce.c3s2.iphmx.comA 68.232.133.93 A 68.232.150.129 A 68.232.139.211 A 68.232.133.91 A 68.232.150.127 A 68.232.139.195 A 68.232.139.213 A 68.232.150.108 A 68.232.139.209 A 68.232.139.212 A 68.232.139.208 A 68.232.133.90 A 68.232.133.92 A 68.232.150.128 A 68.232.139.196 A 68.232.139.210esa8.rolls-royce.c3s2.iphmx.com ✓ esa14.rolls-royce.c3s2.iphmx.com ✓ esa12.rolls-royce.c3s2.iphmx.com ✓ esa3.rolls-royce.c3s2.iphmx.com ✓ esa7.rolls-royce.c3s2.iphmx.com ✓ esa4.rolls-royce.c3s2.iphmx.com ✓ esa16.rolls-royce.c3s2.iphmx.com ✓ esa9.rolls-royce.c3s2.iphmx.com ✓ esa10.rolls-royce.c3s2.iphmx.com ✓ esa15.rolls-royce.c3s2.iphmx.com ✓ esa6.rolls-royce.c3s2.iphmx.com ✓ esa2.rolls-royce.c3s2.iphmx.com ✓ esa1.rolls-royce.c3s2.iphmx.com ✓ esa13.rolls-royce.c3s2.iphmx.com ✓ esa5.rolls-royce.c3s2.iphmx.com ✓ esa11.rolls-royce.c3s2.iphmx.com ✓
20mx2.rolls-royce.c3s2.iphmx.comA 68.232.133.93 A 68.232.139.208 A 68.232.139.212 A 68.232.139.213 A 68.232.150.108 A 68.232.150.129 A 68.232.139.195 A 68.232.150.128 A 68.232.150.127 A 68.232.139.210 A 68.232.139.209 A 68.232.133.92 A 68.232.133.91 A 68.232.139.196 A 68.232.133.90 A 68.232.139.211esa8.rolls-royce.c3s2.iphmx.com ✓ esa6.rolls-royce.c3s2.iphmx.com ✓ esa15.rolls-royce.c3s2.iphmx.com ✓ esa16.rolls-royce.c3s2.iphmx.com ✓ esa9.rolls-royce.c3s2.iphmx.com ✓ esa14.rolls-royce.c3s2.iphmx.com ✓ esa4.rolls-royce.c3s2.iphmx.com ✓ esa13.rolls-royce.c3s2.iphmx.com ✓ esa7.rolls-royce.c3s2.iphmx.com ✓ esa11.rolls-royce.c3s2.iphmx.com ✓ esa10.rolls-royce.c3s2.iphmx.com ✓ esa1.rolls-royce.c3s2.iphmx.com ✓ esa3.rolls-royce.c3s2.iphmx.com ✓ esa5.rolls-royce.c3s2.iphmx.com ✓ esa2.rolls-royce.c3s2.iphmx.com ✓ esa12.rolls-royce.c3s2.iphmx.com ✓

Checks

  • ✓ 4 MX records #9
    Found 4 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: mxa-004f7902.gslb.pphosted.com, mxb-004f7902.gslb.pphosted.com, mx1.rolls-royce.c3s2.iphmx.com, mx2.rolls-royce.c3s2.iphmx.com
    #11
  • ✓ Redundant MX hosts #12
    Found 4 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 4 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 34 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mxa-004f7902.gslb.pphosted.comnone-
mxb-004f7902.gslb.pphosted.comnone-
mx1.rolls-royce.c3s2.iphmx.comnone-
mx2.rolls-royce.c3s2.iphmx.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