Skip to content

Hostname

lnkus.net

Last fetched

lnkus.net resolves to 3.213.30.243, announced in 3.208.0.0/12 by AMAZON-AES - Amazon.com, Inc. in US. lnkus.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 · lnkus.netRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/lnkus.net

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
identity protection service
Contact emails
080e08d6-4ce1-41dd-a545-ab4cbe8b1cf3@identity-protect.org, 0fdfa3cc-b7cf-425e-af37-7b52bff5b731@identity-protect.org, 240d13a8-d5de-45c5-b224-a079deebcfa6@identity-protect.org, 8bb0bdb6-1cb9-4897-b497-512496b38a6c@identity-protect.org, a1fc24ed-01b4-4293-a1c6-2dce28d9445f@identity-protect.org, d0395495-dbb4-4353-8174-8d87a3767c85@identity-protect.org, f3615d34-81a8-445c-9c8c-49fced0e9815@identity-protect.org, owner-7541699@lnkus.net.whoisprivacyservice.org

Mail and authentication

Nameservers

  • ns-144.awsdns-18.com
  • ns-573.awsdns-07.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
  • ns-1528.awsdns-63.org
  • ns-1690.awsdns-19.co.uk

Threat-feed evidence

History

Related pages

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