Skip to content

Hostname

chtq.net

Last fetched

chtq.net resolves to 160.16.200.77, announced in 160.16.128.0/17 by SAKURA-B - SAKURA Internet Inc. in JP. chtq.net is listed by 1 threat feed; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 1 threat feed. At least one source recommends blocking.

Threat feeds listing this
1
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:45:24 GMT
Last seen on a feed
Tue, 22 Sep 2026 23:26:40 GMT

Nutrition Label

WHISPER CANON · chtq.netRouting diversity2.4/10Peering density4.7/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency10.0/10Resolver footprint8.6/10canon.whisper.security/host/chtq.net

Resolution chain

IPv6 resolution

No AAAA record for chtq.net is recorded in WhisperGraph.

Attribution

sakura

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
privacy service provided by withheld for privacy ehf
Contact emails
18980816667@189.cn, c75da9a8380b4b568d1ac022b89e6df7.protect@withheldforprivacy.com

Subdomains

Subdomain
dscriy.chtq.net
system.chtq.net
updata.chtq.net

Showing 3 of 6. View all subdomains →

Mail and authentication

Nameservers

  • dns1.registrar-servers.com
  • dns101.registrar-servers.com
  • dns102.registrar-servers.com
  • dns2.registrar-servers.com
  • ns1.value-domain.com
  • ns2.value-domain.com
  • a.gtld-servers.net
  • b.gtld-servers.net
  • c.gtld-servers.net
  • d.gtld-servers.net
  • e.gtld-servers.net
  • f.gtld-servers.net
  • g.gtld-servers.net
  • h.gtld-servers.net
  • i.gtld-servers.net
  • j.gtld-servers.net
  • k.gtld-servers.net
  • l.gtld-servers.net
  • m.gtld-servers.net

MX records

  • mx.plingest.com
  • eforward1.registrar-servers.com
  • eforward2.registrar-servers.com
  • eforward3.registrar-servers.com
  • eforward4.registrar-servers.com
  • eforward5.registrar-servers.com

SPF policy

  • include: spf.efwd.registrar-servers.com

Threat-feed evidence

History

Related pages

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