Skip to content

Hostname

sherv.net

Last fetched

sherv.net resolves to 172.234.24.211, announced in 172.234.16.0/20 by AKAMAI-LINODE-AP - Akamai Connected Cloud in US. sherv.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 · sherv.netRouting diversity2.4/10Peering density6.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.5/10canon.whisper.security/host/sherv.net

Resolution chain

IPv6 resolution

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

Attribution

akamai

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
whoisguard protected
Contact emails
378b21091bc645fab39c91fc33775bd2.protect@whoisguard.com, 65bfc117a3e647928b1ca1c0623944d6.protect@whoisguard.com, af561d84514d4f0a88025298409a2fab.protect@whoisguard.com, b2f7f9e2643d41b3a997b33936fb7cc5.protect@whoisguard.com, d6a52cdcaff944608c44d85b85ea35d2.protect@whoisguard.com

Subdomains

Subdomain
mail.sherv.net
www.sherv.net

Showing 2 of 8. 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

Sample outbound links

Mail and authentication

Nameservers

  • dns101.registrar-servers.com
  • dns102.registrar-servers.com
  • cdns1.interserver.net
  • cdns2.interserver.net
  • cdns3.interserver.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

  • mx.plingest.com
  • mail.sherv.net

Threat-feed evidence

History

Related pages

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