Hostname
edenly.com
Last fetched
edenly.com resolves to 2 IPv4 addresses operated by CLOUDFLARENET - Cloudflare, Inc. in CA. WHOIS lists iana:433 as the registrar.
Nutrition Label
Resolution chain
edenly.com resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 172.66.40.87 | 172.66.40.0/21 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 172.66.43.169 | 172.66.40.0/21 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
WHOIS identity
- Registrar
- iana:433
- Organization
- suzor edwin
- Contact emails
- 1n6rezt47mxfljiwin0l@a.o-w-o.info
- 1wuzk5qvgm54lktvkzeq@x.o-w-o.info
- 2ygmtgi41g3ao18z2tvh@p.o-w-o.info
- bl5m7vw2kskmxzbkhdne@l.o-w-o.info
- by7pjlbhtth1lh0rokik@n.o-w-o.info
- d3a12eedp4hbj5kvnuol@s.o-w-o.info
- r505tkxjsv77qv85l5oe@z.o-w-o.info
- t1zdngj1x69xyz0w7tu3@k.o-w-o.info
- uu7fxyc7f9ekkgeslljx@a.o-w-o.info
- v3wsifz293fcjhca18b8@d.o-w-o.info
- z9b4drl0itpxw2cflw53@h.o-w-o.info
Subdomains
82 observed subdomains of edenly.com.
Showing 25 of 82. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from edenly.com in the public web crawl.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
7 SPF mechanisms authorising senders for edenly.com.
| Mechanism | Target |
|---|---|
| SPF_A | edenly.com |
| SPF_INCLUDE | mailgun.org |
| SPF_INCLUDE | sendgrid.net |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_IP | 34.77.173.211 |
| SPF_IP | 35.187.69.202 |
| SPF_MX | edenly.com |
Related pages
Pivot deeper into the graph from edenly.com.
- IP · 172.66.40.87
- ASN · AS13335CLOUDFLARENET - Cloudflare, Inc.
- Registrar · iana:433
- Country · CA
- Email · 1n6rezt47mxfljiwin0l@a.o-w-o.info
- TLD · .com
- Browse hostnames · ed…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "edenly.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.