Skip to content

Hostname

lexmangas.com

Last fetched

lexmangas.com resolves to 209.141.44.103, announced in 209.141.32.0/19 by PONYNET - FranTech Solutions in US. lexmangas.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 · lexmangas.comRouting diversity2.4/10Peering density8.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/lexmangas.com

Resolution chain

IPv6 resolution

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

Attribution

frantech

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
privacy service provided by withheld for privacy ehf
Contact emails
21546498a3f143ccba67a4508cc996bf.protect@whoisguard.com, c583d1bf683d4c3a8981141585807113.protect@withheldforprivacy.com

Subdomains

Subdomain
mail.lexmangas.com
subdomi.lexmangas.com
www.lexmangas.com

Showing 3 of 4. 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

  • airi.azk1.net
  • marina.azk1.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

  • lexmangas.com

SPF policy

  • a: lexmangas.com
  • mx: lexmangas.com
  • include: relay.mailbaby.net
  • ip: 107.181.240.34
  • ip: 107.189.31.193
  • ip: 135.181.160.229
  • ip: 206.168.190.119
  • ip: 209.141.44.103
  • ip: 65.108.198.210

Threat-feed evidence

History

Related pages

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