Skip to content

Hostname

maanta.fr

Last fetched

maanta.fr resolves to 37.9.233.17, announced in 37.9.224.0/20 by SEEWEB - SEEWEB s.r.l. in IT. maanta.fr 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 · maanta.frRouting diversity2.4/10Peering density6.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/maanta.fr

Resolution chain

IPv6 resolution

No AAAA record for maanta.fr is recorded in WhisperGraph.

Attribution

seeweb

ORIGIN_AS

WHOIS identity

Registrar
registrar:ovh
Registrant organisation
bega srl
Contact emails
ru34oya6ylwdafynw7is@i.o-w-o.info

Subdomains

Subdomain
www.maanta.fr

Showing 1 of 1 subdomain (1 per page).

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

  • dns104.ovh.net
  • ns104.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

  • 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
  • include: mx.ovh.com
  • include: spf.turbo-smtp.com
  • a: maanta.fr
  • mx: maanta.fr
  • include: cs01.maanta.it
  • include: servers.mcsv.net
  • ip: 185.63.41.203
  • ip: 37.9.233.17
  • ip: 80.241.142.124
  • ip: 80.241.142.83
  • ip: 95.110.229.76

Threat-feed evidence

History

Related pages

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