Skip to content

Hostname

lipid.org

Last fetched

lipid.org resolves to 158.85.124.89, announced in 158.85.64.0/18 by SOFTLAYER - IBM Cloud in CA. lipid.org 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 · lipid.orgRouting diversity1.5/10Peering density8.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.5/10canon.whisper.security/host/lipid.org

Resolution chain

IPv6 resolution

No AAAA record for lipid.org is recorded in WhisperGraph.

Attribution

ibm

ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
clark morgan
Contact emails
cmorgan@leadingstar.com, cseymour@leadingstar.com

Subdomains

Subdomain
beta.lipid.org
db.lipid.org
mail.lipid.org
media.lipid.org
webmail.lipid.org
www.lipid.org

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

Sample outbound links

Mail and authentication

Nameservers

  • ns1.softlayer.com
  • ns1.theplanet.com
  • ns2.theplanet.com
  • ns5.ev1servers.net
  • ns6.ev1servers.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

  • lipid.org.1.arsmtp.com
  • lipid.org.2.arsmtp.com

SPF policy

  • ip: 158.85.122.165/32
  • include: webassessor.com
  • include: servers.mcsv.net
  • include: sendgrid.net
  • a: lipid.org
  • mx: lipid.org

Threat-feed evidence

History

Related pages

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