Skip to content

Hostname

orsay.pl

Last fetched

orsay.pl resolves to 185.59.211.205, announced in 185.59.208.0/22 by VSHOSTING - VSHOSTING-CDN in CZ. orsay.pl 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 · orsay.plRouting diversity1.5/10Peering density5.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.8/10canon.whisper.security/host/orsay.pl

Resolution chain

IPv6 resolution

No AAAA record for orsay.pl is recorded in WhisperGraph.

Attribution

vshosting

ORIGIN_AS

WHOIS identity

Registrar
registrar:corporation service company
Registrant organisation
orsay international s.r.o.

Subdomains

Subdomain
b2b.orsay.pl
com.orsay.pl
sgtm.orsay.pl
targito.orsay.pl
track.orsay.pl
track2.orsay.pl
wildcard.orsay.pl
www.orsay.pl

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

  • ns1.netim.net
  • ns2.netim.net
  • ns3.netim.net
  • ns1.netnames.net
  • ns2.netnames.net
  • ns5.netnames.net
  • ns6.netnames.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

  • orsay-pl.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • include: spf.netdirect.cz
  • include: spf.seznam.cz
  • mx: orsay.pl
  • ip: 185.59.210.33
  • ip: 185.59.210.79
  • ip: 194.145.183.14
  • ip: 217.16.180.22

Threat-feed evidence

History

Related pages

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