Skip to content

Hostname

4nparis.com

Last fetched

4nparis.com resolves to 95.211.233.237, announced in 95.211.0.0/16 by LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V. in NL. 4nparis.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 · 4nparis.comRouting diversity1.5/10Peering density3.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/4nparis.com

Resolution chain

IPv6 resolution

No AAAA record for 4nparis.com is recorded in WhisperGraph.

Attribution

leaseweb netherlands

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:1387
Registrant organisation
frana?ois quentin
Contact emails
godaddy@mavenhosting.com, quentin@fonctionsdesign.com, info@domain-contact.org

Subdomains

Subdomain
cpcalendars.4nparis.com
mail.4nparis.com
webdisk.4nparis.com
www.4nparis.com

Showing 4 of 4 subdomains (4 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

  • 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
  • ns1eu.service-dns.net
  • ns2eu.service-dns.net
  • ns3eu.service-dns.net

MX records

  • 4nparis.com

SPF policy

  • ip: 51.91.192.124/32
  • ip: 51.38.41.19/32
  • ip: 51.91.19.77/24
  • a: 4nparis.com
  • mx: 4nparis.com
  • include: spf.likuid.com
  • ip: 5.196.83.142
  • ip: 91.121.136.164
  • ip: 95.211.233.237

Threat-feed evidence

History

Related pages

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