Skip to content

Hostname

autosphere.fr

Last fetched

autosphere.fr resolves to 152.89.172.56, announced in 152.89.172.0/23 by NAMESHIELDGRP - NAMESHIELD SAS in FR. autosphere.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 · autosphere.frRouting diversity2.4/10Peering density3.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.2/10canon.whisper.security/host/autosphere.fr

Resolution chain

IPv6 resolution

Attribution

nameshield

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
registrar:nameshield
Registrant organisation
emil frey motors france
Contact emails
postmaster@pgamotors.com, dsi@emilfrey.fr

Subdomains

Subdomain
auto360-app.autosphere.fr
auto360-ws.autosphere.fr
auto360.autosphere.fr
blog.autosphere.fr
carte-cadeau-classics.autosphere.fr
cdn-photos.autosphere.fr
classics.autosphere.fr
delivery.autosphere.fr
dev-myform.autosphere.fr
devisassurance.autosphere.fr
email.autosphere.fr
er.autosphere.fr

Showing 12 of 60. 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

  • nsb.perf1.com
  • nsc.perf1.com
  • nsz.perf1.com
  • nsa.perf1.fr
  • nsz.perf1.fr

MX records

  • de-smtp-inbound-1.mimecast.com
  • de-smtp-inbound-2.mimecast.com
  • mx-eff1.emilfrey.fr
  • mx-eff2.emilfrey.fr

SPF policy

  • include: o1.email.citnow.com
  • include: o2.email.citnow.com
  • include: eskerondemand.com
  • include: spf.mailjet.com
  • include: spf.protection.outlook.com
  • mx: autosphere.fr
  • include: mailgun.org
  • include: eu.mailgun.org
  • include: _spf.profils.org

Threat-feed evidence

History

Related pages

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