Mail domain report: sitejabber.com

SPF

pass

SPF record published

Found

Record: v=spf1 mx a ip4:167.89.0.0/17 ip4:208.117.48.0/20 ip4:50.31.32.0/19 ip4:198.37.144.0/20 ip4:198.21.0.0/21 ip4:192.254.112.0/20 ip4:168.245.0.0/17 ip4:149.72.0.0/16 ip4:159.183.0.0/16 ip4:185.41.28.0/22 ip4:94.143.16.0/21 ip4:185.24.144.0/22 ip4:153.92.224.0/19 ip4:213.32.128.0/18 ip4:185.107.232.0/22 ip4:77.32.128.0/18 ip4:77.32.192.0/19 ip4:212.146.192.0/18 ip4:172.246.0.0/18 include:_netblocks.google.com include:_netblocks2.google.com include:_netblocks3.google.com include:_spf.salesforce.com -all
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).
✓ 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.sitejabber.com)

Found

Record: v=DMARC1; p=quarantine; pct=100; rua=mailto:re+kq4jnqcwxwp@dmarc.postmarkapp.com,mailto:tech.evgenii@gmail.com; sp=none; aspf=r; adkim=r
Found at: _dmarc.sitejabber.com
External report address: mailto:re+kq4jnqcwxwp@dmarc.postmarkapp.com (authorized)
External report address: mailto:tech.evgenii@gmail.com (not authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
sp	none	Subdomain policy
pct	100	Percentage of mail the policy applies to
rua	mailto:re+kq4jnqcwxwp@dmarc.postmarkapp.com,mailto:tech.evgenii@gmail.com	Aggregate report addresses
adkim	r	DKIM alignment (r = relaxed, s = strict)
aspf	r	SPF alignment (r = relaxed, s = strict)

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:re+kq4jnqcwxwp@dmarc.postmarkapp.com, mailto:tech.evgenii@gmail.com
!

Subdomains unprotected (sp=none)

DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.

#20
!

Report address not authorized

These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:tech.evgenii@gmail.com (needs sitejabber.com._report._dmarc.gmail.com). Ask the report provider to publish the record, or check the address.

#29

DKIM

warn

Selectors: mail, selector1, google, s1, s2

Found

Selectors: mail, selector1, google, s1, s2
_domainkey: NXDOMAIN

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

Checks

✓ Keys found: mail, selector1, google, s1, s2 #7

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

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), selector1 (1024 bits), google (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

7 mail servers

Found

Priority	Host	Records	Reverse DNS
1	aspmx.l.google.com	A 142.251.127.27 AAAA 2a00:1450:4001:c21::1a	lcfrai-in-f27.1e100.net ✓ lcfrai-in-f26.1e100.net ✓
5	alt1.aspmx.l.google.com	A 142.250.147.26 AAAA 2a00:1450:4025:c01::1b	rd-in-f26.1e100.net ✓ rd-in-f27.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::1b	rd-in-f26.1e100.net ✓ rd-in-f27.1e100.net ✓
10	aspmx3.googlemail.com	A 172.253.152.26 AAAA 2a00:1450:4010:c22::1a	yulpptr-in-f26.1e100.net ✓ yulpptr-in-f26.1e100.net ✓
30	aspmx4.googlemail.com	A 192.179.20.26 AAAA 2404:6800:4000:1027::1b	ncboms-in-f26.1e100.net ✓ ncboms-in-f27.1e100.net ✓
30	aspmx5.googlemail.com	A 192.178.158.26 AAAA 2404:6800:4013:813::1b	lcdels-in-f26.1e100.net ✓ lcdels-in-f27.1e100.net ✓

Checks

✓ 7 MX records #9

Found 7 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 7 MX records, which provides redundancy for email delivery.
!

More than 5 MX records

Found 7 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.

#13
✓ 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 14 MX addresss have a PTR record that resolves back to them.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 7 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	-
aspmx4.googlemail.com	none	-
aspmx5.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

fail

https://www.sitejabber.com/img/branding/profile.svg

Found

Record: v=BIMI1; l=https://www.sitejabber.com/img/branding/profile.svg; a=;
Found at: default._bimi.sitejabber.com
Logo: https://www.sitejabber.com/img/branding/profile.svg

Checks

!

No certificate (a=)

The logo is published without a Verified Mark Certificate. Gmail and Apple Mail only show BIMI logos with a VMC or CMC; Yahoo shows it without one.

#38
✗

DMARC not strict enough for BIMI

Mail clients will not show the logo. BIMI requires a subdomain policy other than sp=none.

#39