Skip to content

Hostname

easerver.net

Last fetched

easerver.net resolves to 91.191.173.78, announced in 91.191.173.0/24 by NETDIREKT-AS - NETDIREKT BILISIM DANISMANLIK ILETISIM HIZMETLERI SANAYI VE TICARET AS in TR. easerver.net 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 · easerver.netRouting diversity1.5/10Peering density6.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint10.0/10canon.whisper.security/host/easerver.net

Resolution chain

IPv6 resolution

No AAAA record for easerver.net is recorded in WhisperGraph.

Attribution

netdirekt bilisim danismanlik iletisim hizmetleri sanayi ve ticaret

ORIGIN_AS

WHOIS identity

Registrar
iana:1454

Subdomains

Mail and authentication

Nameservers

  • ns1.easerver.net
  • ns110.easerver.net
  • ns111.easerver.net
  • ns120.easerver.net
  • ns121.easerver.net
  • ns122.easerver.net
  • ns123.easerver.net
  • ns125.easerver.net
  • ns126.easerver.net
  • ns2.easerver.net
  • ns3.easerver.net
  • ns4.easerver.net
  • ns41.easerver.net
  • ns42.easerver.net
  • ns5.easerver.net
  • ns6.easerver.net
  • ns7.easerver.net
  • ns8.easerver.net
  • ns96.easerver.net
  • ns97.easerver.net
  • ns98.easerver.net
  • ns99.easerver.net
  • park.easerver.net
  • yenileme.easerver.net
  • 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

  • 93.187.200.112.easerver.net
  • mail.easerver.net

Threat-feed evidence

History

Related pages

Pivot from easerver.net 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: "easerver.net"})-[: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.