Hostname
headq.io
Last fetched
headq.io resolves to 31.43.160.6, announced in 31.43.160.0/24 by AMAZON-02 - Amazon.com, Inc. in NL. headq.io 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
- 31.43.160.6
31.43.160.0/24 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 31.43.161.6
31.43.161.0/24 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 34.159.15.243
34.159.0.0/17 · GOOGLE-CLOUD-PLATFORM - Google LLC · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for headq.io is recorded in WhisperGraph.
Attribution
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:48
Subdomains
| Subdomain |
|---|
| developers.headq.io |
| production-store.headq.io |
| resources.headq.io |
| staging-store.headq.io |
| status.headq.io |
| support.headq.io |
| test.headq.io |
| test1.headq.io |
| test2.headq.io |
| test3.headq.io |
| www.headq.io |
Showing 11 of 11 subdomains (11 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
- dns3.louhi.fi
- dns1.louhi.net
- dns2.louhi.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
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- include: _spf.google.com
- a: headq.io
Threat-feed evidence
History
Related pages
Pivot from headq.io 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: "headq.io"})-[: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.