Mail domain report: worktribe.com

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:185.249.69.192/26 ip4:5.57.63.208/28 ip4:95.217.45.122 ip4:65.109.63.209 ip4:65.108.103.11 ip4:167.99.80.32 ip4:65.108.231.123 ip4:199.164.192.207/32 ip4:198.102.221.207/32 ip4:199.164.192.208/32 ip4:199.164.192.211/32 ip4:199.247.49.211/32 ip4:199.164.192.212/32 ip4:208.118.70.226/32 include:_spf.google.com ~all
DNS lookups: 1 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 1 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=reject (_dmarc.worktribe.com)

Found

Record: v=DMARC1;p=reject;pct=100;ri=86400;fo=s;
Found at: _dmarc.worktribe.com

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
pct	100	Percentage of mail the policy applies to
fo	s	Failure reporting options
ri	86400	Report interval (seconds)

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.
!

No aggregate reports (rua)

DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...

#19
✓ Subdomain policy: reject #20

Subdomains are covered by policy 'reject'.

DKIM

warn

No keys found under the checked selectors

Found

Selectors: None found
_domainkey: NOERROR

Checks

!

No key under common selectors

The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.

#7

DNSSEC

warn

Signed, but no DS at parent

Found

DNSKEY records: Yes (2)
DS at parent: No
Algorithms: ECDSAP256SHA256 (13)
Key tags: 34505, 2371
Signatures valid until: 19 December 2026, 12:18 UTC

Checks

!

Signed, but no DS at parent

The zone is signed (DNSKEY present) but the parent has no DS record, so the chain of trust is incomplete. Publish the DS record at your registrar.

#8
✓ Signatures valid until 2026-12-19 #21

DNSKEY signatures are valid until 2026-12-19T12:18:58Z.

MX

pass

4 mail servers

Found

Priority	Host	Records	Reverse DNS
1	smtp.google.com	A 142.251.127.26 A 142.251.127.27 AAAA 2a00:1450:4001:c21::1b AAAA 2a00:1450:4001:c21::1a	lcfrai-in-f26.1e100.net ✓ lcfrai-in-f27.1e100.net ✓ lcfrai-in-f27.1e100.net ✓ lcfrai-in-f26.1e100.net ✓
50	aspmx.l.google.com	A 142.251.127.27 AAAA 2a00:1450:4001:c21::1b	lcfrai-in-f27.1e100.net ✓ lcfrai-in-f27.1e100.net ✓
100	alt1.aspmx.l.google.com	A 142.250.147.27 AAAA 2a00:1450:4025:c01::1a	rd-in-f27.1e100.net ✓ rd-in-f26.1e100.net ✓
100	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 ✓

Checks

✓ 4 MX records #9

Found 4 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 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 10 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 host	TLSA	DNSSEC
smtp.google.com	none	-
aspmx.l.google.com	none	-
alt1.aspmx.l.google.com	none	-
alt2.aspmx.l.google.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