Hostname

api.conversion.io

Last fetched Sun, 13 Sep 2026 16:47:52 GMT

api.conversion.io resolves to 162.159.140.98, announced in 162.159.128.0/19 by CLOUDFLARENET - Cloudflare, Inc. in CA. api.conversion.io 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

Resolution chain

162.159.140.98
162.159.128.0/19 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
172.66.0.96
172.66.0.0/22 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
18.153.232.22
18.153.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
18.158.23.165
18.156.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
18.195.173.109
18.194.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
3.124.114.60
3.124.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
3.64.220.154
3.64.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
52.59.30.105
52.58.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
63.181.220.63
63.180.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
63.181.39.183
63.180.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
63.185.99.89
63.184.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
63.186.233.151
63.184.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE

IPv6 resolution

No AAAA record for api.conversion.io is recorded in WhisperGraph.

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for api.conversion.io. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Mail and authentication

Nameservers

ns-337.awsdns-42.com
ns-917.awsdns-50.net
ns-1435.awsdns-51.org
ns-1626.awsdns-11.co.uk

Threat-feed evidence

History

Pivot from api.conversion.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: "api.conversion.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 20

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