Skip to content

Hostname

mynet.pro

Last fetched

mynet.pro resolves to 109.173.124.74, announced in 109.173.0.0/17 by NCNET-AS - PJSC Rostelecom in RU. mynet.pro 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 · mynet.proRouting diversity1.5/10Peering density4.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/mynet.pro

Resolution chain

IPv6 resolution

No AAAA record for mynet.pro is recorded in WhisperGraph.

Attribution

pjsc rostelecom

ORIGIN_AS

WHOIS identity

Registrar
iana:303
Registrant organisation
evgenii smagin
Contact emails
sev2910@yandex.ru

Subdomains

Subdomain
liftek.mynet.pro
lkm.mynet.pro
lp.mynet.pro
mx1.mynet.pro
ns1.mynet.pro
ns2.mynet.pro
ns3.mynet.pro
ns4.mynet.pro
sb.mynet.pro
sp.mynet.pro
vestra.mynet.pro
vhs.mynet.pro

Showing 12 of 13. View all subdomains →

Mail and authentication

Nameservers

  • ns1.mynet.pro
  • ns2.mynet.pro
  • ns3.mynet.pro
  • ns4.mynet.pro

Threat-feed evidence

History

Related pages

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