Skip to content

Hostname

industrialzone.com

Last fetched

industrialzone.com resolves to 209.59.154.54, announced in 209.59.128.0/18 by LIQUIDWEB - Liquid Web, L.L.C in US. industrialzone.com 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 · industrialzone.comRouting diversity1.5/10Peering density4.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/industrialzone.com

Resolution chain

IPv6 resolution

No AAAA record for industrialzone.com is recorded in WhisperGraph.

Attribution

liquid

ORIGIN_AS

WHOIS identity

Registrar
iana:636
Registrant organisation
private registration
Contact emails
61xqhj5tpbkwjtmm@private-contact.com, 6mj3ningmi0e2n88@private-contact.com, agn3kk0dw7sacw9j@private-contact.com, cqwo3q2hv3sfqk9x@private-contact.com, nv52mblzgoq2x6ue@private-contact.com, szyaa42iaepvklcn@private-contact.com, v1fdpobpoutwwf9q@private-contact.com, vlv0agga9br5kzym@private-contact.com, whc23k9vemj56rnn@private-contact.com, yikalbdrfyayuam0@private-contact.com, yvtjwx9h31d9yxbg@private-contact.com

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns1.industrialzone.com
  • ns2.industrialzone.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

  • mail.industrialzone.com

SPF policy

  • a: industrialzone.com
  • mx: industrialzone.com
  • ip: 209.59.154.54

Threat-feed evidence

History

Related pages

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