Skip to content

Hostname

digitex.net

Last fetched

digitex.net resolves to 96.39.210.10, announced in 96.39.208.0/20 by CHARTER-20115 - Charter Communications LLC in US. digitex.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 · digitex.netRouting diversity1.5/10Peering density8.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.8/10canon.whisper.security/host/digitex.net

Resolution chain

IPv6 resolution

Attribution

charter

ORIGIN_AS

WHOIS identity

Registrar
iana:69
Registrant organisation
digitex.com,
Contact emails
webmaster@digitex.net

Subdomains

Subdomain
accounting-pc.digitex.net
alpha.digitex.net
alvwtswitch.digitex.net
bill.digitex.net
digitexcom.digitex.net
dns01.digitex.net
dns1.digitex.net
dns2.digitex.net
dns3.digitex.net
dns4.digitex.net
dts01.digitex.net
dts05.digitex.net

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

  • alpha.digitex.net
  • dns01.digitex.net
  • dns4.digitex.net
  • ns01.digitex.net
  • ns1.digitex.net
  • ns2.digitex.net
  • zeus.digitex.net
  • 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

  • mx.digitex.net.cust.b.hostedemail.com

SPF policy

  • include: _spf.hostedemail.com
  • mx: digitex.net
  • include: spf.visp.net

Threat-feed evidence

History

Related pages

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