Skip to content

Hostname

ljmcmenemy.com

Last fetched

ljmcmenemy.com resolves to 57.129.144.46, announced in 57.129.128.0/17 by OVH - OVH SAS in GB. ljmcmenemy.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 · ljmcmenemy.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.0/10canon.whisper.security/host/ljmcmenemy.com

Resolution chain

IPv6 resolution

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

Attribution

ovh

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:1387
Contact emails
ljmcmenemy.com@contactprivacy.com, gdpr-masking@gdpr-masked.com

Subdomains

Mail and authentication

Nameservers

  • ns1.serverhostgroup.com
  • ns2.serverhostgroup.com
  • ns3.serverhostgroup.com

MX records

  • ljmcmenemy.com

SPF policy

  • a: ljmcmenemy.com
  • mx: ljmcmenemy.com
  • include: relay.mailchannels.net

Threat-feed evidence

History

Related pages

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