Mail domain report: tucows.com

SPF

fail

SPF record published

Found

Record: v=spf1 ip4:216.40.44.0/24 ip4:216.40.34.9/32 ip4:216.40.42.17/32 ip4:64.99.140.0/24 ip4:34.195.55.186 ip4:216.40.35.66 ip6:2600:1f18:6057:5c01::16 include:_spf.zdsys.com include:mail.zendesk.com include:docebosaas.com include:servers.mcsv.net include:mg-spf.greenhouse.io include:20704235.spf08.hubspotemail.net include:343165382.spf03.hubspotemail.net include:email.freshservice.com ?all
DNS lookups: 19 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
✗

19 DNS lookups, over the limit of 10

SPF record needs 19 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.

#2
!

Ends with ?all (neutral)

SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.

#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.
✓ No overly broad IP ranges #27

All ip4/ip6 ranges are narrow enough.

DMARC

fail

p=none (_dmarc.tucows.com)

Found

Record: v=DMARC1; p=none; rua=mailto:dmarc-rua@abuse.tucows.com; ruf=mailto:dmarc-ruf@abuse.tucows.com; fo=0; adkim=r; aspf=r; pct=100; rf=afrf; ri=86400; sp=none
Found at: _dmarc.tucows.com

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
sp	none	Subdomain policy
pct	100	Percentage of mail the policy applies to
rua	mailto:dmarc-rua@abuse.tucows.com	Aggregate report addresses
ruf	mailto:dmarc-ruf@abuse.tucows.com	Failure report addresses
adkim	r	DKIM alignment (r = relaxed, s = strict)
aspf	r	SPF alignment (r = relaxed, s = strict)
fo	0	Failure reporting options
rf	afrf	Failure report format
ri	86400	Report interval (seconds)

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:dmarc-rua@abuse.tucows.com
✓ Report addresses in own domain #29

All report addresses are in your own organizational domain.

DKIM

warn

Selectors: mail, k1, google

Found

Selectors: mail, k1, google
_domainkey: NOERROR

Selector	Key	Flags
mail	RSA 2048 bits
k1	RSA 1024 bits
google	RSA 2048 bits

Checks

✓ Keys found: mail, k1, google #7

DKIM keys found for this domain with selectors: mail, k1, google
!

1024-bit DKIM key

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

Priority	Host	Records	Reverse DNS
0	mx.tucows.com.cust.hostedemail.com	A 216.40.42.4	mx.hostedemail.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: mx.tucows.com.cust.hostedemail.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 1 MX address 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 host	TLSA	DNSSEC
mx.tucows.com.cust.hostedemail.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