Skip to content

Hostname

mygo.pro

Last fetched

mygo.pro resolves to 91.102.135.39, announced in 91.102.135.0/24 by NETSTORMING-WHL-AS - NETSTORMING S.R.L. in IT. mygo.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 · mygo.proRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.0/10canon.whisper.security/host/mygo.pro

Resolution chain

IPv6 resolution

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

Attribution

netstorming

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:81
Registrant organisation
gowide world eurl
Contact emails
28700b824a3fd6a0c2dd5d02bd8ba9f7-1577695@contact.gandi.net, c42442f5965af6f15fe49374e19a3394-8405289@contact.gandi.net

Subdomains

Subdomain
autodiscover.mygo.pro
b2b.mygo.pro
connect.mygo.pro
cpanel.mygo.pro
dev.mygo.pro
email.mygo.pro
helpdesk.mygo.pro
kalima.mygo.pro
mail.mygo.pro
myg.mygo.pro
ns1.mygo.pro
ns2.mygo.pro

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

  • ns.aicgroup.biz
  • ns1.mygo.pro
  • ns2.mygo.pro

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com
  • smtp.google.com

SPF policy

  • ip: 5.252.44.0/22
  • ip: 213.32.172.210/32
  • ip: 2a01:7140::0/32
  • ip: 2a05:ca40::0/29
  • ip: 2a09:4340::/48
  • ip: 77.32.210.38/32
  • include: _spf.google.com
  • include: spf.sendinblue.com
  • a: mygo.pro
  • mx: mygo.pro
  • ip: 149.202.69.116
  • ip: 41.230.16.199

Threat-feed evidence

History

Related pages

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