Hostname

bitcointradingpro.com

Last fetched Sat, 26 Sep 2026 19:48:08 GMT

bitcointradingpro.com resolves to 172.234.24.211, announced in 172.234.16.0/20 by AKAMAI-LINODE-AP - Akamai Connected Cloud in US. bitcointradingpro.com 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

172.234.24.211
172.234.16.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
172.239.57.117
172.239.32.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
192.64.119.18
192.64.119.0/24 · NAMECHEAP-NET - Namecheap, Inc. · Atlanta, US
52.201.53.166
52.200.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
98.82.42.139
98.80.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US

IPv6 resolution

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar: iana:1068
Registrant organisation: alex joyner
Contact emails: bitcointradingpro.com@superprivacyservice.com, joyneralex@hotmail.com, mryu88@gmail.com, mryu99@gmail.com, 03cb5bb0a4724780b1dcb22b339a2207.protect@withheldforprivacy.com, 9f355ca4dfd744318477ed36a1f43078.protect@withheldforprivacy.com, reactivation-pending@mail.withheldforprivacy.com

Subdomains

Subdomain
mail.bitcointradingpro.com
www.bitcointradingpro.com

Showing 2 of 2 subdomains (2 per page).

Mail and authentication

Nameservers

ns1.namebrightdns.com
ns2.namebrightdns.com
nsg1.namebrightdns.com
nsg2.namebrightdns.com
dns1.registrar-servers.com
dns101.registrar-servers.com
dns102.registrar-servers.com
dns2.registrar-servers.com

MX records

mx.plingest.com
eforward1.registrar-servers.com
eforward2.registrar-servers.com
eforward3.registrar-servers.com
eforward4.registrar-servers.com
eforward5.registrar-servers.com

SPF policy

include: spf.efwd.registrar-servers.com

Threat-feed evidence

History

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

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