Skip to content

Hostname

hostingspace.ro

Last fetched

hostingspace.ro resolves to 195.88.81.90, announced in 195.88.81.0/24 by SPACE-AS - Space Ro SRL in RO. hostingspace.ro 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 · hostingspace.roRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/hostingspace.ro

Resolution chain

IPv6 resolution

No AAAA record for hostingspace.ro is recorded in WhisperGraph.

Attribution

space ro

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
registrar:jordan tech srl

Subdomains

Subdomain
autodiscover.hostingspace.ro
beta.hostingspace.ro
blog.hostingspace.ro
core1.hostingspace.ro
core2.hostingspace.ro
core2old.hostingspace.ro
core3.hostingspace.ro
core3demo.hostingspace.ro
core3testing.hostingspace.ro
core4.hostingspace.ro
cpanel.hostingspace.ro
cpcalendars.hostingspace.ro

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

  • 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
  • ns1.hostingspace.ro
  • ns2.hostingspace.ro
  • ns3.hostingspace.ro
  • ns4.hostingspace.ro

MX records

  • hostingspace.ro

SPF policy

  • a: hostingspace.ro
  • mx: hostingspace.ro
  • ip: 195.88.81.28
  • ip: 195.88.81.90

Threat-feed evidence

History

Related pages

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