Skip to content

Hostname

usakochan.net

Last fetched

usakochan.net resolves to 192.157.56.141, announced in 192.157.56.0/22 by SERVER-MANIA - B2 Net Solutions Inc. in US. usakochan.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 · usakochan.netRouting diversity3.5/10Peering density3.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint7.8/10canon.whisper.security/host/usakochan.net

Resolution chain

IPv6 resolution

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

Attribution

nforce entertainment

ORIGIN_AS

WHOIS identity

Registrar
iana:1479
Registrant organisation
whois protection, this company does not own this domain name s.r.o.
Contact emails
admin@domainregistriesfoundation.com, usakochan.net@fablovkawhoisprotection.com, pw-2547490f351c7ba3bf7b8016ffa7d7e0@privacyguardian.org, pw-8c494ea5b2a0044fe3564830046f7730@privacyguardian.org, pw-df9ed4a931fa240a6271a07ad71ed298@privacyguardian.org, pw-e7aa5719822779899d6ba22ce1aefa05@privacyguardian.org

Subdomains

Subdomain
wildcard.usakochan.net
ww1.usakochan.net
www.usakochan.net

Showing 3 of 3 subdomains (3 per page).

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

  • ns1.brainydns.com
  • ns2.brainydns.com
  • ns1.dingodns.com
  • ns2.dingodns.com
  • ns1.emu-dns.com
  • ns1.kirklanddc.com
  • ns2.kirklanddc.com
  • ns1.koaladns.com
  • ns2.koaladns.com
  • ns1.magpiedns.com
  • ns2.magpiedns.com
  • ns1.numbatdns.com
  • ns2.numbatdns.com
  • ns1.squirreldns.com

Threat-feed evidence

History

Related pages

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