Hostname
lemon-treehouse.com
Last fetched
lemon-treehouse.com resolves to 198.54.115.91, announced in 198.54.115.0/24 by NAMECHEAP-NET - Namecheap, Inc. in US. lemon-treehouse.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
IPv6 resolution
No AAAA record for lemon-treehouse.com is recorded in WhisperGraph.
Attribution
namecheap
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1479
- Registrant organisation
- domain admin
- Contact emails
- reg_15281643@whoisprotection.cc, domreg@leohee.com, pw-052604b2e64d4b2cde826566ddcae7c5@privacyguardian.org
Subdomains
| Subdomain |
|---|
| cpanel.lemon-treehouse.com |
| cpcalendars.lemon-treehouse.com |
| cpcontacts.lemon-treehouse.com |
| mail.lemon-treehouse.com |
| webdisk.lemon-treehouse.com |
| webmail.lemon-treehouse.com |
| www.lemon-treehouse.com |
Showing 7 of 7 subdomains (7 per page).
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
- dns1.namecheaphosting.com
- dns2.namecheaphosting.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
MX records
- mx1-hosting.jellyfish.systems
- mx2-hosting.jellyfish.systems
- mx3-hosting.jellyfish.systems
SPF policy
- a: lemon-treehouse.com
- mx: lemon-treehouse.com
- include: spf.web-hosting.com
- ip: 198.54.114.91
- ip: 198.54.115.91
Threat-feed evidence
History
Related pages
Pivot from lemon-treehouse.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: "lemon-treehouse.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.