Skip to content

Hostname

tergenit.ws

Last fetched

tergenit.ws resolves to 141.193.23.32, announced in 141.193.23.0/24 by HAWKHOST - Hawk Host Inc. in CA. tergenit.ws 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 · tergenit.wsRouting diversity3.0/10Peering density3.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.6/10canon.whisper.security/host/tergenit.ws

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · MAIL_RECEIVER, ORIGIN_AS, CDN

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for tergenit.ws. 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
autodiscover.tergenit.ws
c280c394c184.tergenit.ws
cpanel.tergenit.ws
cpcalendars.tergenit.ws
cpcontacts.tergenit.ws
mail.tergenit.ws
webdisk.tergenit.ws
webmail.tergenit.ws
www.tergenit.ws

Showing 9 of 10. View all subdomains →

Mail and authentication

Nameservers

  • ns1.arandomserver.com
  • ns2.arandomserver.com
  • marjory.ns.cloudflare.com
  • vick.ns.cloudflare.com
  • ns13.hawkhost.com
  • ns14.hawkhost.com
  • 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

  • tergenit.ws
  • _dc-mx.c280c394c184.tergenit.ws

SPF policy

  • include: _spf.arandomserver.com
  • a: tergenit.ws
  • mx: tergenit.ws
  • ip: 172.96.191.165
  • ip: 172.96.191.9

Threat-feed evidence

History

Related pages

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