Mail domain report: virginmoney.com

SPF

pass

SPF record published

Found

Record: v=spf1 include:spf.messagelabs.com include:spf.protection.outlook.com include:_spf.salesforce.com a:mx.tsyseurope.com ip4:80.244.181.180 ip4:80.169.167.27 include:sendgrid.net ip4:209.61.151.0/24 ip4:166.78.68.0/22 ip4:198.61.254.0/23 ip4:192.237.158.0/23 ip4:23.253.182.0/23 ip4:104.130.96.0/28 ip4:146.20.113.0/24 ip4:146.20.191.0/24 ip4:159.135.224.0/20 ip4:69.72.32.0/20 ip4:141.193.32.0/23 ip4:159.135.140.80/29 ip4:159.135.132.128/25 ip4:161.38.204.0/22 ip4:87.253.232.0/21 ip4:185.189.236.0/22 ip4:185.211.120.0/22 ip4:185.250.236.0/22 ip4:143.55.236.0/22 ip4:198.244.60.0/22 ip4:168.245.8.67 ip4:149.72.132.11 ip4:149.72.208.47 ip4:149.72.237.97 ip4:193.32.46.48 ip4:193.32.48.48 ip4:199.255.192.0/22 ip4:199.127.232.0/22 ip4:54.240.0.0/18 ip4:69.169.224.0/20 ip4:23.249.208.0/20 ip4:23.251.224.0/19 ip4:76.223.176.0/20 ip4:54.240.64.0/19 ip4:54.240.96.0/19 ip4:52.82.172.0/22 ip4:76.223.128.0/19 ip4:147.253.211.147 ip4:62.172.139.91 ip4:62.172.139.92 ip4:213.120.244.91 ip4:149.72.213.47 ip4:168.245.38.49 include:amazonses.com ip4:88.211.24.174 ip4:88.211.26.174 ~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.virginmoney.com)

Found

Record: v=DMARC1; p=reject; rua=mailto:clydesdale-bank-plc@rua.agari.com,mailto:virginmoney@rua.netcraft.com,mailto:dmarcalerts@virginmoney.com; ruf=mailto:clydesdale-bank-plc@ruf.agari.com,mailto:virginmoney@ruf.netcraft.com
Found at: _dmarc.virginmoney.com
External report address: mailto:clydesdale-bank-plc@rua.agari.com (authorized)
External report address: mailto:virginmoney@rua.netcraft.com (authorized)
External report address: mailto:clydesdale-bank-plc@ruf.agari.com (authorized)
External report address: mailto:virginmoney@ruf.netcraft.com (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
rua	mailto:clydesdale-bank-plc@rua.agari.com,mailto:virginmoney@rua.netcraft.com,mailto:dmarcalerts@virginmoney.com	Aggregate report addresses
ruf	mailto:clydesdale-bank-plc@ruf.agari.com,mailto:virginmoney@ruf.netcraft.com	Failure 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:clydesdale-bank-plc@rua.agari.com, mailto:virginmoney@rua.netcraft.com, mailto:dmarcalerts@virginmoney.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: selector1, s1, s2

Found

Selectors: selector1, s1, s2
_domainkey: NOERROR

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

Checks

✓ Keys found: selector1, s1, s2 #7

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

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: 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

2 mail servers

Found

Priority	Host	Records	Reverse DNS
10	cluster3.eu.messagelabs.com	A 195.245.230.193 A 85.158.142.209 A 195.245.231.73 A 195.245.230.199 A 85.158.142.218 A 195.245.231.64	mail851.messagelabs.com ✓ mail833.messagelabs.com ✓ mail877.messagelabs.com ✓ mail857.messagelabs.com ✓ mail831.messagelabs.com ✓ mail870.messagelabs.com ✓
20	cluster3a.eu.messagelabs.com	A 34.91.159.228	228.159.91.34.bc.googleusercontent.com ✓

Checks

✓ 2 MX records #9

Found 2 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: cluster3.eu.messagelabs.com, cluster3a.eu.messagelabs.com

#11
✓ Redundant MX hosts #12

Found 2 MX records, which provides redundancy for email delivery.
✓ At most 5 MX records #13

Found 2 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 7 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
cluster3.eu.messagelabs.com	none	-
cluster3a.eu.messagelabs.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