Skip to content

Hostname

api.ybug.io

Last fetched

api.ybug.io resolves to 2 IPv4 addresses operated by AKAMAI-LINODE-AP Akamai Connected Cloud in DE.

Nutrition Label

WHISPER CANON · api.ybug.ioRouting diversityPeering densityMOAS conflictThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/host/api.ybug.io

Resolution chain

api.ybug.io resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
172.105.78.47172.105.64.0/19AS63949AKAMAI-LINODE-AP Akamai Connected CloudDE
46.224.230.8846.224.0.0/15AS24940HETZNER-ASDE

WHOIS identity

No WHOIS records are currently associated with api.ybug.io in WhisperGraph.

Subdomains

1 observed subdomain of api.ybug.io.

Threat posture

History

Mail and authentication

SPF policy

5 SPF mechanisms authorising senders for api.ybug.io.

MechanismTarget
SPF_Aapi.ybug.io
SPF_IP172.105.78.47
SPF_IP45.79.249.137/32
SPF_IP46.224.230.88
SPF_MXapi.ybug.io

Related pages

Pivot deeper into the graph from api.ybug.io.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "api.ybug.io"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
      -[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.