Skip to content

Hostname

servers.ly

Last fetched

servers.ly resolves to 69.72.248.199, announced in 69.72.248.0/24 by WHG-LON - WHG Hosting Services Ltd in GB. servers.ly 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 · servers.lyRouting diversity1.5/10Peering density5.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/servers.ly

Resolution chain

IPv6 resolution

No AAAA record for servers.ly is recorded in WhisperGraph.

Attribution

whg

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
registrar:libyan elite co.
Registrant organisation
servers
Contact emails
info@serverlibya.com

Subdomains

Subdomain
autodiscover.servers.ly
cpanel.servers.ly
cpcalendars.servers.ly
cpcontacts.servers.ly
mail.servers.ly
ns1.servers.ly
ns2.servers.ly
webdisk.servers.ly
webmail.servers.ly
whm.servers.ly
www.servers.ly

Showing 11 of 11 subdomains (11 per page).

Mail and authentication

Nameservers

  • ns1.serverlibya.com
  • ns2.serverlibya.com
  • ns3.serverlibya.com
  • ns4.serverlibya.com
  • 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

  • servers.ly

SPF policy

  • include: spf.antispamcloud.com
  • include: spf.mysecurecloudhost.com
  • a: servers.ly
  • mx: servers.ly
  • include: relay.mailchannels.net
  • ip: 181.214.31.79
  • ip: 192.250.234.236
  • ip: 62.169.21.213
  • ip: 69.72.248.199

Threat-feed evidence

History

Related pages

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