Skip to content

Hostname

lexogrine.com

Last fetched

lexogrine.com resolves to 13.249.182.13, announced in 13.249.182.0/23 by AMAZON-02 - Amazon.com, Inc. in US. lexogrine.com 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 · lexogrine.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/lexogrine.com

Resolution chain

IPv6 resolution

No AAAA record for lexogrine.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:433
Registrant organisation
majka michal
Contact emails
53sy9zgqdq1d0spgllzj@x.o-w-o.info, qzi8hdotwi1zaq4iw3ps@w.o-w-o.info, y7irgdi6rmjtxav3c2u4@b.o-w-o.info

Subdomains

Subdomain
autoreels-api-dev.lexogrine.com
blog-api.lexogrine.com
gamemaps-api.lexogrine.com
glhf-dev-admin.lexogrine.com
glhf-dev-api-store.lexogrine.com
glhf-dev-search.lexogrine.com
glhf-dev-store.lexogrine.com
glhf-dev.lexogrine.com
glhf-staging-admin.lexogrine.com
glhf-staging-api-store.lexogrine.com
glhf-staging-search.lexogrine.com
glhf-staging-store.lexogrine.com

Showing 12 of 26. 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-40.awsdns-05.com
  • ns-637.awsdns-15.net
  • ns-1247.awsdns-27.org
  • ns-1879.awsdns-42.co.uk

MX records

  • inbound-smtp.us-east-1.amazonaws.com
  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: _spf.google.com

Threat-feed evidence

History

Related pages

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