Hostname
halotechs.com
Last fetched
halotechs.com resolves to 185.186.169.201, announced in 185.186.221.0/24 by LOADING - Grupo Loading Systems, S.L. in ES. halotechs.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
IPv6 resolution
No AAAA record for halotechs.com is recorded in WhisperGraph.
Attribution
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- on behalf of halotechs.com owner
- Contact emails
- halotechs.com@domainsbyproxy.com, desarrollo@livall.eu, 677b99f1-7a31-493a-a459-a65c8d4595d3@identity-protect.org, 6ee62a68-a912-4a8e-8964-f158a620a10c@identity-protect.org, a8db0cc1-2b45-417b-a06a-26255270c7cc@identity-protect.org, e77ac642-6291-4bdc-9a4b-f2b7b1227fb0@identity-protect.org
Subdomains
Showing 3 of 3 subdomains (3 per page).
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
- ns-311.awsdns-38.com
- ns1.controldeservidor.com
- ns2.controldeservidor.com
- ns3.controldeservitor.com
- ns-1008.awsdns-62.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
- ns-1350.awsdns-40.org
- ns-1606.awsdns-08.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
Threat-feed evidence
History
Related pages
Pivot from halotechs.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: "halotechs.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.