Skip to content

Hostname

edgenet.com

Last fetched

edgenet.com resolves to 213.159.133.85, announced in 213.159.132.0/23 by COEOSOLUTIONS - Coeo Solutions, LLC in US. edgenet.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 · edgenet.comRouting diversity1.5/10Peering density2.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/edgenet.com

Resolution chain

IPv6 resolution

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

Attribution

coeo

ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
j.d. meek
Contact emails
jdmeek@edgenet.com, ndavis@edgenet.com, 689085f3-48f4-4b00-8362-0d9111bb36dd@identity-protect.org, 9b28ed6e-02f1-43c9-9273-b7e387fff7e5@identity-protect.org, b892b131-7ca9-4ec3-8ef7-22110a326e59@identity-protect.org

Subdomains

Subdomain
2g.edgenet.com
api.edgenet.com
assets.edgenet.com
autodiscover.edgenet.com
connectbeta.edgenet.com
daofficenorth.edgenet.com
daofficesouth.edgenet.com
daprodsouth.edgenet.com
data.edgenet.com
dealersupport.edgenet.com
demo.edgenet.com
em.edgenet.com

Showing 12 of 61. 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

Mail and authentication

Nameservers

  • ns-344.awsdns-43.com
  • ns-923.awsdns-51.net
  • ns-1242.awsdns-27.org
  • ns-1956.awsdns-52.co.uk

MX records

  • edgenet-com.mail.protection.outlook.com

SPF policy

  • ip: 147.160.247.0/24
  • ip: 128.136.45.0/24
  • ip: 52.114.159.40/32
  • include: spf.autopilothq.com
  • include: spf.protection.outlook.com
  • include: aspmx.pardot.com
  • include: sendgrid.net
  • ip: 50.233.71.18

Threat-feed evidence

History

Related pages

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