Skip to content

Hostname

tradeupspy.com

Last fetched

tradeupspy.com resolves to 13.227.192.23, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. tradeupspy.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

WHISPER CANON · tradeupspy.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/tradeupspy.com

Resolution chain

IPv6 resolution

No AAAA record for tradeupspy.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of tradeupspy.com owner
Contact emails
111bd5d7-311b-4822-adc1-f9335a855017@identity-protect.org, 124dbcb3-dc46-4f3d-be9d-2ef1fc65206d@identity-protect.org, 2f7707b1-cb6c-4107-8f3c-75f8af6b9d85@identity-protect.org, 4bfbde6b-e1a7-42e3-8fdd-cbcb199dcdc2@identity-protect.org, 62a4fcb1-aab8-41ce-88a7-86c63bb1e4cd@identity-protect.org, 964d57c5-b837-457c-befe-db27e7e7a3dd@identity-protect.org, owner-11261548@tradeupspy.com.whoisprivacyservice.org

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

Nameservers

  • ns-369.awsdns-46.com
  • ns-625.awsdns-14.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
  • ns-1385.awsdns-45.org
  • ns-1826.awsdns-36.co.uk

Threat-feed evidence

History

Related pages

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