Skip to content

Hostname

lyte.dev

Last fetched

lyte.dev resolves to 18.208.88.157, announced in 18.208.0.0/13 by AMAZON-AES - Amazon.com, Inc. in US. lyte.dev 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 · lyte.devRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint9.4/10canon.whisper.security/host/lyte.dev

Resolution chain

IPv6 resolution

No AAAA record for lyte.dev is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
privacy service provided by withheld for privacy ehf
Contact emails
17e4ee4d9ee2440e989c35623640fd38.protect@withheldforprivacy.com

Subdomains

Subdomain
a.lyte.dev
api.lyte.dev
audio.lyte.dev
bw.lyte.dev
chat.lyte.dev
deno.lyte.dev
files.lyte.dev
git.lyte.dev
h.lyte.dev
mail.lyte.dev
matrix.lyte.dev
ourcraft.lyte.dev

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

  • ns0.1984.is
  • ns1.1984.is
  • ns2.1984.is
  • ns1.he.net
  • ns2.he.net
  • ns3.he.net
  • ns4.he.net
  • ns5.he.net
  • dns1.p02.nsone.net
  • dns2.p02.nsone.net
  • dns3.p02.nsone.net
  • dns4.p02.nsone.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

  • mxa.mailgun.org
  • mxb.mailgun.org
  • pebble.lyte.dev

SPF policy

  • include: mailgun.org

Threat-feed evidence

History

Related pages

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