Skip to content

Hostname

itx.web.id

Last fetched

itx.web.id resolves to 131.153.46.120, announced in 131.153.46.0/24 by PHOENIXNAP-AS-SG1 - PhoenixNAP in SG. itx.web.id 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 · itx.web.idRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.5/10canon.whisper.security/host/itx.web.id

Resolution chain

IPv6 resolution

No AAAA record for itx.web.id is recorded in WhisperGraph.

Attribution

phoenixnap

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:1
Registrant organisation
personal
Contact emails
itoxte@yahoo.com

Subdomains

Subdomain
admin.itx.web.id
albizia.itx.web.id
bombax.itx.web.id
calotropis.itx.web.id
en.itx.web.id
forum.itx.web.id
mail.itx.web.id
ns1.itx.web.id
ns2.itx.web.id
ns3.itx.web.id
themes.itx.web.id
www.itx.web.id

Showing 12 of 13. 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

Sample outbound links

Mail and authentication

Nameservers

  • sgp1.myprivatedns.com
  • sgp2.myprivatedns.com
  • usa1.myprivatedns.com
  • usa2.myprivatedns.com
  • usa3.myprivatedns.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

  • itx.web.id

SPF policy

  • a: itx.web.id
  • mx: itx.web.id
  • ip: 103.243.172.242
  • ip: 103.243.172.243
  • ip: 104.237.63.178
  • ip: 131.153.46.120

Threat-feed evidence

History

Related pages

Pivot from itx.web.id 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: "itx.web.id"})-[: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.