Skip to content

Hostname

data393.net

Last fetched

data393.net resolves to 208.42.234.28, announced in 208.42.224.0/19 by DATABANK-LATISYS - Latisys-Denver, LLC in GB. data393.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 · data393.netRouting diversity1.5/10Peering density4.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint9.3/10canon.whisper.security/host/data393.net

Resolution chain

IPv6 resolution

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

Attribution

latisys denver

ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
data 393
Contact emails
dns-admin@data393.com

Subdomains

Subdomain
acsinc.data393.net
anm.data393.net
disecurityco.data393.net
dns01.data393.net
dns02.data393.net
dnsmng.data393.net
dtsinc.data393.net
eng01.data393.net
ftp.data393.net
gateway.data393.net
hydra.data393.net
jabber1.data393.net

Showing 12 of 87. View all subdomains →

Mail and authentication

Nameservers

  • ns1.dfw.databank.com
  • ns2.dfw.databank.com
  • ns1.iad.databank.com
  • ns2.iad.databank.com
  • ns1.msp.databank.com
  • ns2.msp.databank.com
  • ns3.databank.com
  • ns4.databank.com
  • ns5.databank.com
  • ns1.slc.databank.com
  • ns2.slc.databank.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

  • data393.com.inbound10.mxlogic.net
  • data393.com.inbound10.mxlogicmx.net

Threat-feed evidence

History

Related pages

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