tcs.com

Checked 22 October 2026, 10:55 UTC · via 8.8.8.8
!Passed with warnings
27 passed 7 warnings 0 failed

SPF

pass

SPF record published

Found

Record
v=spf1 include:_spf1.tcs.com include:_spf2.tcs.com include:_spf3.tcs.com include:_spf4.tcs.com include:mktomail.com -all
DNS lookups
5 of 10
Void lookups
0 of 2

Checks

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

pass

p=reject (_dmarc.tcs.com)

Found

Record
v=DMARC1; p=reject; pct=100; rua=mailto:f22ff518@mxtoolbox.dmarc-report.com,mailto:rua.dmarc@tcs.com; ruf=mailto:f22ff518@forensics.dmarc-report.com,mailto:ruf.dmarc@tcs.com; fo=1
Found at
_dmarc.tcs.com
External report address
mailto:f22ff518@mxtoolbox.dmarc-report.com (authorized)
External report address
mailto:f22ff518@forensics.dmarc-report.com (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
pct100Percentage of mail the policy applies to
ruamailto:f22ff518@mxtoolbox.dmarc-report.com,mailto:rua.dmarc@tcs.comAggregate report addresses
rufmailto:f22ff518@forensics.dmarc-report.com,mailto:ruf.dmarc@tcs.comFailure report addresses
fo1Failure reporting options

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.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:f22ff518@mxtoolbox.dmarc-report.com, mailto:rua.dmarc@tcs.com
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: google, s1, s2

Found

Selectors
google, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
googleRSA 2048 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

  • ✓ Keys found: google, s1, s2 #7
    DKIM keys found for this domain with selectors: google, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: 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

Signed, DS published at parent

Found

DNSKEY records
Yes (4)
DS at parent
Yes
Algorithms
RSASHA256 (8)
Key tags
16145, 23191, 58213, 12088
Signatures valid until
23 October 2026, 23:48 UTC

Checks

  • ✓ Signed, DS published at parent #8
    DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
  • !
    Signatures expire in 37h0m0s
    DNSKEY signatures expire at 2026-10-23T23:48:16Z (in 37h0m0s). Check that re-signing works.
    #21

MX

warn

14 mail servers

Found

PriorityHostRecordsReverse DNS
10Inblrg04.tcs.comA 121.242.48.30Inblrg04.tcs.com ✓
10Inblrg05.tcs.comA 121.242.48.31Inblrg05.tcs.com ✓
10Inmumg04.tcs.comA 45.249.218.97no PTR
10Inmumg05.tcs.comA 45.249.218.122no PTR
10inblrg01.tcs.comA 121.242.48.3inblrg01.tcs.com ✓
10inblrg03.tcs.comA 121.242.48.29Inblrg03.tcs.com ✓
10inchng01.tcs.comA 122.184.60.13inchng01.tcs.com ✓
10inchng02.tcs.comA 122.184.60.14inchng02.tcs.com ✓
10inchng04.tcs.comA 122.184.60.109inchng04.tcs.com ✓
10inchng05.tcs.comA 122.184.60.134inchng05.tcs.com ✓
10inmumg01.tcs.comA 219.64.33.12inmumg01.tcs.com ✓
10inmumg02.tcs.comA 219.64.33.222Inmumg02.tcs.com ✓
10uklong01.tcs.comA 80.82.129.165uklong01.tcs.com ✓
10usnjyg01.tcs.comA 208.44.114.64usnjyg01.tcs.com ✓

Checks

  • ✓ 14 MX records #9
    Found 14 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: Inblrg04.tcs.com, Inblrg05.tcs.com, Inmumg04.tcs.com, Inmumg05.tcs.com, inblrg01.tcs.com, inblrg03.tcs.com, inchng01.tcs.com, inchng02.tcs.com, inchng04.tcs.com, inchng05.tcs.com, inmumg01.tcs.com, inmumg02.tcs.com, uklong01.tcs.com, usnjyg01.tcs.com
    #11
  • ✓ Redundant MX hosts #12
    Found 14 MX records, which provides redundancy for email delivery.
  • !
    More than 5 MX records
    Found 14 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.
  • !
    Addresses without reverse DNS
    These MX addresses have no PTR record, which many receivers treat as a spam signal: 45.249.218.97 (Inmumg04.tcs.com), 45.249.218.122 (Inmumg05.tcs.com). Ask your hosting provider to set one.
    #30

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
Inblrg04.tcs.com3 1 1 0c9dc34ad73fa434… 3 1 1 1b4dd1717733f2d6…Yes
Inblrg05.tcs.com3 1 1 1b4dd1717733f2d6… 3 1 1 0c9dc34ad73fa434…Yes
Inmumg04.tcs.com3 1 1 1b4dd1717733f2d6… 3 1 1 0c9dc34ad73fa434…Yes
Inmumg05.tcs.com3 1 1 1b4dd1717733f2d6… 3 1 1 0c9dc34ad73fa434…Yes
inblrg01.tcs.com3 1 1 0c9dc34ad73fa434… 3 1 1 1b4dd1717733f2d6…Yes
inblrg03.tcs.com3 1 1 1b4dd1717733f2d6… 3 1 1 0c9dc34ad73fa434…Yes
inchng01.tcs.com3 1 1 1b4dd1717733f2d6… 3 1 1 0c9dc34ad73fa434…Yes
inchng02.tcs.com3 1 1 0c9dc34ad73fa434… 3 1 1 1b4dd1717733f2d6…Yes
inchng04.tcs.com3 1 1 0c9dc34ad73fa434… 3 1 1 1b4dd1717733f2d6…Yes
inchng05.tcs.com3 1 1 1b4dd1717733f2d6… 3 1 1 0c9dc34ad73fa434…Yes
inmumg01.tcs.com3 1 1 1b4dd1717733f2d6… 3 1 1 0c9dc34ad73fa434…Yes
inmumg02.tcs.com3 1 1 1b4dd1717733f2d6… 3 1 1 0c9dc34ad73fa434…Yes
uklong01.tcs.com3 1 1 0c9dc34ad73fa434… 3 1 1 1b4dd1717733f2d6…Yes
usnjyg01.tcs.com3 1 1 0c9dc34ad73fa434… 3 1 1 1b4dd1717733f2d6…Yes

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
  • !
    Not configured
    MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".
    #35
  • ✓ DANE on all MX hosts #36
    All 14 MX hosts publish DNSSEC-validated TLSA records.

BIMI

pass

https://bimi.ssl.com/mc-b51l5e8a153.svg

Found

Record
v=BIMI1; l=https://bimi.ssl.com/mc-b51l5e8a153.svg; a=https://bimi.ssl.com/mc-b51l5e8a153.pem
Found at
default._bimi.tcs.com
Logo
https://bimi.ssl.com/mc-b51l5e8a153.svg
Certificate
https://bimi.ssl.com/mc-b51l5e8a153.pem

Checks

  • ✓ Logo and certificate published #38
    BIMI logo: https://bimi.ssl.com/mc-b51l5e8a153.svg; certificate: https://bimi.ssl.com/mc-b51l5e8a153.pem
  • ✓ DMARC meets BIMI requirements #39
    DMARC is enforced on all mail, as BIMI requires.