Skip to content

Hostname

mencorner.com

Last fetched

mencorner.com resolves to 178.251.206.8, announced in 178.251.200.0/21 by OCTOPUCE-AS - Octopuce s.a.r.l. in FR. mencorner.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 · mencorner.comRouting diversity1.5/10Peering density5.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/mencorner.com

Resolution chain

IPv6 resolution

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

Attribution

octopuce

ORIGIN_AS

WHOIS identity

Registrar
iana:433
Registrant organisation
karine schrenzel
Contact emails
1ad0fe13fd73ab84ae5b0106e0260dbf-618120@contact.gandi.net, d8c683f68086ac00b949ccaaec8aba83-618120@contact.gandi.net

Subdomains

Subdomain
back.mencorner.com
beaute.mencorner.com
de.mencorner.com
es.mencorner.com
it.mencorner.com
preprod.mencorner.com
tss.mencorner.com
www.mencorner.com

Showing 8 of 9. 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

  • dns20.ovh.net
  • ns20.ovh.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

  • mta-gw.infomaniak.ch

SPF policy

  • a: mencorner.com
  • mx: mencorner.com
  • include: spf.splio.com
  • include: spf.shopinvest.fr

Threat-feed evidence

History

Related pages

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