Skip to content

Hostname

mysrv.cloud

Last fetched

mysrv.cloud is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. mysrv.cloud 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 · mysrv.cloudRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.9/10canon.whisper.security/host/mysrv.cloud

Resolution chain

No IPv4 resolution is recorded for mysrv.cloud in WhisperGraph.

IPv6 resolution

No AAAA record for mysrv.cloud is recorded in WhisperGraph.

WHOIS identity

Registrar
iana:1390
Registrant organisation
domains by proxy,
Contact emails
leon.marte.100@gmail.com

Subdomains

Subdomain
altctrl-node-sg.mysrv.cloud
altctrl-node.mysrv.cloud
aws-backup.mysrv.cloud
blackbox-staging.mysrv.cloud
broken-recipe.mysrv.cloud
ccommunity-pools.mysrv.cloud
certum-wp.mysrv.cloud
ch4k1pu-node.mysrv.cloud
communiity-pools.mysrv.cloud
community-pools.mysrv.cloud
dero-api.mysrv.cloud
dero-linode-uk.mysrv.cloud

Showing 12 of 93. View all subdomains →

Mail and authentication

Nameservers

  • ns-58.awsdns-07.com
  • ns-138.awsdns-17.com
  • ns-709.awsdns-24.net
  • ns-772.awsdns-32.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
  • ns-1381.awsdns-44.org
  • ns-1413.awsdns-48.org
  • ns-1593.awsdns-07.co.uk
  • ns-1768.awsdns-29.co.uk

MX records

  • mail.protonmail.ch
  • mailsec.protonmail.ch

SPF policy

  • include: _spf.protonmail.ch
  • mx: mysrv.cloud

Threat-feed evidence

History

Related pages

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