Skip to content

Hostname

tsua.net

Last fetched

tsua.net resolves to 185.56.232.212, announced in 185.56.232.0/22 by ADVANCEDHOSTERS-AS - DataWeb Global Group B.V. in NL. tsua.net 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 · tsua.netRouting diversity1.5/10Peering density6.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/tsua.net

Resolution chain

IPv6 resolution

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

Attribution

dataweb global group

ORIGIN_AS

WHOIS identity

Registrar
iana:1418
Registrant organisation
danesco trading
Contact emails
tsua.net@whoisprotectservice.net, hostmaster@imena.ua

Subdomains

Subdomain
12.tsua.net
13.tsua.net
136.tsua.net
137.tsua.net
138.tsua.net
139.tsua.net
140.tsua.net
141.tsua.net
142.tsua.net
143.tsua.net
144.tsua.net
145.tsua.net

Showing 12 of 3,465. View all subdomains →

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Mail and authentication

Nameservers

  • 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
  • ns.lmd.in.ua
  • ns1.itcons.net.ua

MX records

  • emx1.tsua.net

SPF policy

  • ip: 212.40.34.13/32
  • include: _spf.google.com
  • a: tsua.net

Threat-feed evidence

History

Related pages

Pivot from tsua.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: "tsua.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.