Skip to content

Hostname

tcs-dc.jp

Last fetched

tcs-dc.jp is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. tcs-dc.jp is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · tcs-dc.jpRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.6/10canon.whisper.security/host/tcs-dc.jp

Resolution chain

No IPv4 resolution is recorded for tcs-dc.jp in WhisperGraph.

IPv6 resolution

No AAAA record for tcs-dc.jp is recorded in WhisperGraph.

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for tcs-dc.jp. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
mail-relay1.tcs-dc.jp
mg.tcs-dc.jp
ns.tcs-dc.jp
ns2.tcs-dc.jp
ns3.tcs-dc.jp
ns4.tcs-dc.jp
ns5.tcs-dc.jp
server50.tcs-dc.jp
spm2.tcs-dc.jp
spm3.tcs-dc.jp
tcsgdcsmtp01.tcs-dc.jp

Showing 11 of 11 subdomains (11 per page).

Mail and authentication

Nameservers

  • dns3.odn.ne.jp
  • ns.tcs-dc.jp
  • ns2.tcs-dc.jp
  • ns3.tcs-dc.jp
  • ns4.tcs-dc.jp
  • ns5.tcs-dc.jp
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • tcsgdcsmtp01.tcs-dc.jp

SPF policy

  • ip: 210.228.161.0/24
  • ip: 101.102.167.0/24

Threat-feed evidence

History

Related pages

Pivot from tcs-dc.jp into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "tcs-dc.jp"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.