Skip to content

Hostname

edisonda.com

Last fetched

edisonda.com resolves to 5.252.230.107, announced in 5.252.228.0/22 by LHPL - LH.pl Sp. z o.o. in PL. edisonda.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 · edisonda.comRouting diversity1.5/10Peering density2.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/edisonda.com

Resolution chain

IPv6 resolution

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

Attribution

lh pl sp

ORIGIN_AS

WHOIS identity

Registrar
iana:269
Registrant organisation
edisonda sp. z o.o.
Contact emails
info@domain-contact.org, marcin.krecioch@edisonda.pl

Subdomains

Subdomain
_dmarc.edisonda.com
_mta-sts.edisonda.com
brand.edisonda.com
ftp.edisonda.com
mail.edisonda.com
pop.edisonda.com
smtp.edisonda.com
www.edisonda.com

Showing 8 of 8 subdomains (8 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

Mail and authentication

Nameservers

  • 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
  • dns.home.pl
  • dns2.home.pl
  • dns3.home.pl

MX records

  • edisonda.home.pl

SPF policy

  • ip: 148.105.0.0/16
  • ip: 198.2.128.0/18
  • ip: 205.201.128.0/20
  • ip: 46.238.107.160/27
  • ip: 217.153.54.160/28
  • a: edisonda.com
  • mx: edisonda.com
  • include: eu._netblocks.mimecast.com
  • include: spf.protection.outlook.com
  • ip: 79.96.56.203

Threat-feed evidence

History

Related pages

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