Mail domain report: sketchup.com

SPF

fail

SPF record published

Found

Record: v=spf1 a include:_spf.salesforce.com include:_spf.google.com include:_spf.centercode.com include:spf.mandrillapp.com include:mktomail.com ip4:199.15.212.0/22 ip4:72.3.185.0/24 ip4:72.32.154.0/24 ip4:72.32.217.0/24 ip4:72.32.243.0/24 ip4:94.236.119.0/26 ip4:37.188.97.188/32 ip4:185.28.196.0/22 ip4:192.28.128.0/18 ip4:103.237.104.0/22 ip6:2a04:35c0::/29 ip4:72.211.26.174 ip4:68.230.241.144 ip4:207.38.45.154 ip4:184.106.161.23 ip4:108.166.4.85 ip4:108.166.4.86 ip4:108.166.13.59 ip4:198.101.168.60 ip4:198.101.168.61 ip4:198.61.141.233 ip4:198.61.141.235 ip4:198.61.141.237 ip4:198.61.246.115 ip4:166.78.78.167 ip4:166.78.67.243 ip4:166.78.203.73 ip4:162.242.186.108 ip4:162.209.50.140 ip4:162.242.186.111 ip4:23.253.7.133 ip4:166.78.103.208 ip4:104.130.80.21 ip4:104.130.80.22 ip4:104.130.80.23 ip4:166.78.224.177 ip4:50.57.31.224 ip4:50.56.2.100 ip4:50.56.2.102 ip4:50.56.2.103 ip4:23.253.3.227 ip4:162.209.25.130 ip4:64.71.148.0/29 ip6:2001:470:1:3c2::/64 ip4:198.2.128.0/24 ip4:198.2.132.0/22 ip4:198.2.136.0/23 ip4:198.2.186.0/23 ip4:205.201.131.128/25 ip4:205.201.134.128/25 ip4:205.201.136.0/23 ip4:205.201.139.0/24 ip4:198.2.180.0/24 ip4:198.2.179.0/24 ip4:198.2.178.0/24 ip4:198.2.177.0/24 ip4:173.203.82.6 ip4:173.203.81.82 ip4:173.203.56.127 ip4:173.203.81.39 ip4:173.203.79.77 ip4:67.23.31.6 ip4:23.253.182.103 ip4:23.253.183.145 ip4:23.253.183.146 ip4:23.253.183.147 ip4:23.253.183.148 ip4:23.253.183.150 ip4:166.78.68.221 ip4:166.78.69.146 ip4:167.89.46.159 ip4:167.89.64.9 ip4:167.89.65.0 ip4:167.89.65.53 ip4:167.89.65.100 ip4:167.89.74.233 ip4:167.89.75.33 ip4:167.89.75.126 ip4:167.89.75.136 ip4:167.89.75.164 ip4:192.237.159.42 ip4:192.237.159.43
DNS lookups: 7 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 7 DNS lookups (limit is 10).
✗

No 'all' mechanism

SPF record doesn't have an 'all' mechanism. Add -all or ~all at the end of your SPF record.

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

Broad IP ranges

These ranges authorize tens of thousands of addresses or more: ip6:2a04:35c0::/29. Check that you really own and send from all of them.

#27

DMARC

fail

p=none (_dmarc.sketchup.com)

Found

Record: v=DMARC1; p=none; rua=mailto:rnd-devops%2Bdmarc@sketchup.com; ruf=mailto:rnd-devops%2Bdmarc@sketchup.com; fo=1;
Found at: _dmarc.sketchup.com

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
rua	mailto:rnd-devops%2Bdmarc@sketchup.com	Aggregate report addresses
ruf	mailto:rnd-devops%2Bdmarc@sketchup.com	Failure report addresses
fo	1	Failure reporting options

Checks

✗

Policy: none (monitoring only)

DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.

#4
✓ Record published #5

DMARC record exists for this domain.
✓ Valid syntax #17

DMARC record syntax is valid.
✓ Aggregate reports enabled #19

Aggregate reports are sent to: mailto:rnd-devops%2Bdmarc@sketchup.com
✓ Report addresses in own domain #29

All report addresses are in your own organizational domain.

DKIM

warn

Selectors: k1, s1, s2

Found

Selectors: k1, s1, s2
_domainkey: NXDOMAIN

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

Checks

✓ Keys found: k1, s1, s2 #7

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

1024-bit DKIM key

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

pass

5 mail servers

Found

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