Skip to content

Hostname

cnt.my

Last fetched

cnt.my resolves to 195.161.21.59, announced in 195.161.0.0/16 by RTCOMM-AS - JSC RTComm.RU in RU. cnt.my 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 · cnt.myRouting diversity1.5/10Peering density5.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint4.6/10canon.whisper.security/host/cnt.my

Resolution chain

IPv6 resolution

No AAAA record for cnt.my is recorded in WhisperGraph.

Attribution

jsc rtcomm ru

ORIGIN_AS

WHOIS identity

Subdomains

Mail and authentication

Nameservers

  • ns-8.awsdns-01.com
  • ns-981.awsdns-58.net
  • ns-1070.awsdns-05.org
  • ns-1982.awsdns-55.co.uk

MX records

  • mail.cnt.my
  • mail1.cnt.my

SPF policy

  • mx: cnt.my

Threat-feed evidence

History

Related pages

Pivot from cnt.my 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: "cnt.my"})-[: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.