Skip to content

Hostname

cryptosavingexpert.com

Last fetched

cryptosavingexpert.com resolves to 13.135.4.203, announced in 13.134.0.0/15 by AMAZON-02 - Amazon.com, Inc. in GB. cryptosavingexpert.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 · cryptosavingexpert.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/cryptosavingexpert.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:895
Registrant organisation
contact privacy inc. customer 1248239611
Contact emails
0k44quemahvm@contactprivacy.email, pw-0effa3c35f47269443d9f52b2343c5e9@privacyguardian.org

Subdomains

Subdomain
academy.cryptosavingexpert.com
api.cryptosavingexpert.com
cms.cryptosavingexpert.com
sentry.cryptosavingexpert.com
staging.cryptosavingexpert.com
teamcity.cryptosavingexpert.com
www.cryptosavingexpert.com

Showing 7 of 9. View all subdomains →

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • cody.ns.cloudflare.com
  • fish.ns.cloudflare.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • a: cryptosavingexpert.com
  • mx: cryptosavingexpert.com
  • include: spf.mandrillapp.com
  • ip: 88.99.204.168

Threat-feed evidence

History

Related pages

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