Mail domain report: tokopedia.com

SPF

pass

SPF record published

Found

Record: v=spf1 include:amazonses.com include:servers.mcsv.net include:_spf.salesforce.com include:83025279.ppspf.net ip4:205.201.128.0/20 ip4:198.2.128.0/18 ip4:148.105.0.0/16 ip4:185.132.182.154/32 ip4:185.183.28.138/32 include:spf.onlarksuite.com -all
DNS lookups: 8 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 8 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.tokopedia.com)

Found

Record: v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@tokopedia.com
Found at: _dmarc.tokopedia.com

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
pct	100	Percentage of mail the policy applies to
rua	mailto:dmarc@tokopedia.com	Aggregate report addresses

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:dmarc@tokopedia.com
✓ Subdomain policy: quarantine #20

Subdomains are covered by policy 'quarantine'.
✓ Report addresses in own domain #29

All report addresses are in your own organizational domain.

DKIM

warn

Selectors: k1, google, s1, s2

Found

Selectors: k1, google, s1, s2
_domainkey: NOERROR

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

Checks

✓ Keys found: k1, google, s1, s2 #7

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

1024-bit DKIM key

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

3 mail servers

Found

Priority	Host	Records	Reverse DNS
1	mx1.bytedance.com	A 35.172.32.95	ec2-35-172-32-95.compute-1.amazonaws.com ✓
5	mx2.bytedance.com	A 122.14.230.154 A 101.126.58.223	no PTR lookup failed
10	mx3.bytedance.com	A 101.126.58.223 A 18.139.153.173 A 122.14.230.154 A 35.172.32.95	lookup failed ec2-18-139-153-173.ap-southeast-1.compute.amazonaws.com ✓ no PTR ec2-35-172-32-95.compute-1.amazonaws.com ✓

Checks

✓ 3 MX records #9

Found 3 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: mx1.bytedance.com, mx2.bytedance.com, mx3.bytedance.com

#11
✓ Redundant MX hosts #12

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

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

Addresses without reverse DNS

These MX addresses have no PTR record, which many receivers treat as a spam signal: 122.14.230.154 (mx2.bytedance.com), 122.14.230.154 (mx3.bytedance.com). Ask your hosting provider to set one.

#30

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
mx1.bytedance.com	none	-
mx2.bytedance.com	none	-
mx3.bytedance.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