Skip to content

Hostname

maplefling.com

Last fetched

maplefling.com resolves to 34.120.185.54, announced in 34.120.0.0/14 by GOOGLE-CLOUD-PLATFORM - Google LLC in US. maplefling.com is listed by 1 threat feed; reconciled level HIGH.

Threat posture

50threat 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:51:26 GMT
Last seen on a feed
Sat, 12 Sep 2026 19:45:18 GMT

Nutrition Label

WHISPER CANON · maplefling.comRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency10.0/10Resolver footprint5.6/10canon.whisper.security/host/maplefling.com

Resolution chain

IPv6 resolution

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

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1387
Registrant organisation
white castle design b.v.
Contact emails
9b65dbaddc@maplefling.com.whoistrustee.com, info@domain-contact.org, 290d29881b51b4594b8543e1ed564a05f46b0180d8d4815f673e90ec3cbab556@maplefling.com.whoisproxy.org, 72da46d01d965d94bc325e72371e60b376fd57c27e93075e323d66677e03da19@maplefling.com.whoisproxy.org, 8f92d21f8cb57df8b60bcb9a7875932bc5e230fd58a7110ce7ab81d435ddcb66@maplefling.com.whoisproxy.org, d618394f440b01ea92129d1c7fbf9460a3c10d7292463de5e69bb436f0883535@maplefling.com.whoisproxy.org, df7e1ca3048497b510b670bad2e573e0485ab738f38d31a04a221df51814b4b3@maplefling.com.whoisproxy.org, ed210dacdd63378bf406cd8a72eb3e8b1603540a02fe8cf516e9b793ad5aea5c@maplefling.com.whoisproxy.org

Subdomains

Mail and authentication

Nameservers

  • ns1.dnsimple.com
  • ns3.dnsimple.com
  • ns1.dnsimple-edge.com
  • ns3.dnsimple-edge.io
  • ns2.dnsimple-edge.net
  • ns4.dnsimple-edge.org

MX records

  • mx1.fiekabln.com

SPF policy

  • include: spf.fiekabln.com
  • include: 136224628.spf2.netcorecloud.net

Threat-feed evidence

History

Related pages

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