tcl.com

Checked 22 October 2026, 10:55 UTC · via 8.8.8.8
!Passed with warnings
24 passed 5 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:spf.tcl.com -all
DNS lookups
6 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 6 of 10 DNS lookups #2
    SPF record needs 6 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.tcl.com)

Found

Record
v=DMARC1; p=quarantine; ruf=mailto:dmarc_ruf@tcl.com; rua=mailto:dmarc_rua@tcl.com
Found at
_dmarc.tcl.com
TagValueMeaning
vDMARC1Version
pquarantinePolicy
ruamailto:dmarc_rua@tcl.comAggregate report addresses
rufmailto:dmarc_ruf@tcl.comFailure 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_rua@tcl.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, selector1

Found

Selectors
k1, selector1
_domainkey
NXDOMAIN
SelectorKeyFlags
k1RSA 1024 bits
selector1RSA 2048 bits

Checks

  • ✓ Keys found: k1, selector1 #7
    DKIM keys found for this domain with selectors: k1, selector1
  • !
    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

4 mail servers

Found

PriorityHostRecordsReverse DNS
5tcl-com.corpsmtp.netA 192.241.217.149inbound-protection-609.corpsmtp.net ✓
10tcl-com.corpsmtp.cnA 47.74.38.124 A 47.74.38.91 A 47.74.223.162 A 47.74.155.178 A 192.241.207.6 A 206.189.7.78 A 192.241.217.149 A 46.101.220.252 A 138.68.75.175 A 206.189.96.192sal702.corpsmtp.net ✓ sal701.corpsmtp.net ✓ sal605.corpsmtp.net ✓ sal606.corpsmtp.net ✓ inbound-protection-608.corpsmtp.net ✓ inbound-protection-606.corpsmtp.net ✓ inbound-protection-609.corpsmtp.net ✓ inbound-protection-604.corpsmtp.net ✓ inbound-protection-605.corpsmtp.net ✓ inbound-protection-607.corpsmtp.net ✓
15mdn.corpemail.netA 47.88.156.124 A 47.88.170.90 A 23.91.98.8 A 159.100.25.163 A 159.100.25.212 A 159.100.25.64 A 188.166.26.239 A 47.74.183.245 A 95.85.54.247sal603.corpemail.net ✓ sal601.corpemail.net ✓ sal605.corpemail.net ✓ dd-cn2-401.corpemail.net ✓ dd-cn2-402.corpemail.net ✓ dd-cn2-101.corpemail.net ✓ inbound-602.protection.corpemail.net ✓ sal604.corpemail.net ✓ inbound-603.protection.corpemail.net ✓
20mdn.corp-email.cnA 178.62.221.58 A 47.74.183.245 A 95.85.28.238 A 188.166.82.68sgcdn94.corpemail.net ✓ sal604.corpemail.net ✓ vip2-fastemail-cn.biz-email.net ✓ inbound-601.protection.corpemail.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.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: tcl-com.corpsmtp.net, tcl-com.corpsmtp.cn, mdn.corpemail.net, mdn.corp-email.cn
    #11
  • ✓ 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 24 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 hostTLSADNSSEC
tcl-com.corpsmtp.netnone-
tcl-com.corpsmtp.cnnone-
mdn.corpemail.netnone-
mdn.corp-email.cnnone-

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