Skip to content

Hostname

ask-mail.com

Last fetched

ask-mail.com resolves to 104.219.250.37, announced in 104.222.35.0/24 by NAMECHEAP-NET - Namecheap, Inc. in US. ask-mail.com is listed by 1 threat feed; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 1 threat feed. At least one source recommends blocking.

Threat feeds listing this
1
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:49:47 GMT
Last seen on a feed
Mon, 14 Sep 2026 23:25:39 GMT

Nutrition Label

WHISPER CANON · ask-mail.comRouting diversity2.4/10Peering density4.7/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/ask-mail.com

Resolution chain

IPv6 resolution

No AAAA record for ask-mail.com is recorded in WhisperGraph.

Attribution

namecheap net

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
ask applications
Contact emails
dataprotected@maskeddetails.com, mark.kashden@mindspark.com, ebc008e8f61842089d0f85f5fbe142aa.protect@withheldforprivacy.com, pw-699f89f8535bdfa3c928401764022977@privacyguardian.org, pw-ac0ae009ab3d1c966424e25f5066edeb@privacyguardian.org

Subdomains

Showing 1 of 1 subdomain (1 per page).

Mail and authentication

Nameservers

  • failed-whois-verification.namecheap.com
  • verify-contact-details.namecheap.com
  • 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
  • ns2.lander.d.parity.domains
  • ns1.lander.d.parity.domains

Threat-feed evidence

History

Related pages

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