Skip to content

Hostname

lemniscus.de

Last fetched

lemniscus.de resolves to 108.156.60.13, announced in 108.156.60.0/22 by AMAZON-02 - Amazon.com, Inc. in IE. lemniscus.de 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 · lemniscus.deRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/lemniscus.de

Resolution chain

IPv6 resolution

No AAAA record for lemniscus.de is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for lemniscus.de. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
_spf.lemniscus.de
ausstelleranmeldung.lemniscus.de
autodiscover.lemniscus.de
help.lemniscus.de
helpdesk.lemniscus.de
matomo.lemniscus.de
mta-sts.lemniscus.de
my.lemniscus.de
mystage.lemniscus.de
piwik.lemniscus.de
prod-vpn.lemniscus.de
relaunch.lemniscus.de

Showing 12 of 21. 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

  • ns-453.awsdns-56.com
  • ns-818.awsdns-38.net
  • ns-1268.awsdns-30.org
  • ns-1594.awsdns-07.co.uk

MX records

  • mxext1.mailbox.org
  • mxext2.mailbox.org
  • mxext3.mailbox.org

SPF policy

  • include: _spf.lemniscus_de._d.easydmarc.pro

Threat-feed evidence

History

Related pages

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