ioerror.us

Threat posture

Threat feeds listing this

0

Verdict coverage

known-clean

Nutrition Label

Resolution chain

• 172.233.219.123

  172.233.208.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US

• 172.233.219.49

  172.233.208.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US

• 172.233.219.78

  172.233.208.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US

• 172.237.146.25

  172.237.128.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US

• 172.237.146.38

  172.237.128.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US

• 172.237.146.8

  172.237.128.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US

• 198.60.193.11

  198.60.193.0/24 · WPX - K Media Tech Ltd. · Chicago, US

IPv6 resolution

No AAAA record for ioerror.us is recorded in WhisperGraph.

Attribution

WHOIS identity

Registrar

iana:1068

Registrant organisation

jp barkley

Contact emails

error10@gmail.com, jpbarks50@gmail.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

Threat-feed evidence

History

Related pages

Pivot from ioerror.us into the addresses, networks and registries it depends on.

• Whisper Internet Directory · Home
• TLD · .com
• Live MOAS conflicts
• IP address · 172.233.219.123
• Prefix · 172.233.208.0/20
• Network · AKAMAI-LINODE-AP - Akamai Connected Cloud
• TLD · .us
• Registrar · iana:1068
• Glossary · What is a hostname?

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "ioerror.us"})-[: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.