Data as of Nov 5, 2026

185.47.131.0/24

1 residential-proxy exit · 30 days

Ginernet S.L.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
7
selling exits here
Oct 6, 2026 – Nov 4, 2026

Exits seen per day

30 observations

Proxy providers listing exits

  • EnigmaProxy
  • FastProxy
  • LudaxProxy
  • NovaProxy
  • Proxiware
  • ProxyEmpire
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
185.47.128.0/22
since Mar 2016
AS59432Hosting1Ginernet S.L.

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
185.47.128.0/221,024ES-GINERNET-20140212Ginernet S.L. (ORG-JMG1-RIPE) · ESALLOCATED PAFeb 12, 2014abuse@ginernet.com
└ 185.47.131.0/24256GINERNETGINERNETLIR-PARTITIONED PAOct 27, 2018abuse@ginernet.com
via ES-GINERNET-20140212
└ 185.47.131.24/304GINERNETGINERNETASSIGNED PAFeb 5, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.28/312GINERNETGINERNETASSIGNED PAFeb 5, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.30/321GINERNETGINERNETASSIGNED PAFeb 5, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.32/321GINERNETGINERNETASSIGNED PASep 5, 2019abuse@ginernet.com
via GINERNET
└ 185.47.131.33/321GINERNETGINERNETASSIGNED PAMar 8, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.34/321GINERNETGINERNETASSIGNED PADec 31, 2021abuse@ginernet.com
via GINERNET
└ 185.47.131.35/321GINERNETGINERNETASSIGNED PAApr 1, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.36/321GINERNETGINERNETASSIGNED PASep 10, 2019abuse@ginernet.com
via GINERNET
└ 185.47.131.37/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.38/321GINERNETGINERNETASSIGNED PAMar 12, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.39/321GINERNETGINERNETASSIGNED PAMar 12, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.40/321GINERNETGINERNETASSIGNED PAMay 5, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.41/321GINERNETGINERNETASSIGNED PANov 14, 2019abuse@ginernet.com
via GINERNET
└ 185.47.131.42/321GINERNETGINERNETASSIGNED PAMar 12, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.43/321GINERNETGINERNETASSIGNED PAMar 12, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.44/321GINERNETGINERNETASSIGNED PANov 14, 2019abuse@ginernet.com
via GINERNET
└ 185.47.131.45/321GINERNETGINERNETASSIGNED PAFeb 10, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.46/321GINERNETGINERNETASSIGNED PAOct 17, 2019abuse@ginernet.com
via GINERNET
└ 185.47.131.47/321GINERNETGINERNETASSIGNED PAOct 17, 2019abuse@ginernet.com
via GINERNET
└ 185.47.131.48/321GINERNETGINERNETASSIGNED PAMar 12, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.49/321GINERNETGINERNETASSIGNED PAJan 15, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.50/321GINERNETGINERNETASSIGNED PAMay 8, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.51/321GINERNETGINERNETASSIGNED PAMar 12, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.52/321GINERNETGINERNETASSIGNED PAMar 12, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.53/321GINERNETGINERNETASSIGNED PAMar 30, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.54/321GINERNETGINERNETASSIGNED PAFeb 10, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.55/321GINERNETGINERNETASSIGNED PAMar 13, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.56/321GINERNETGINERNETASSIGNED PAMar 13, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.57/321HOSTOWEBHOSTOWEBASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.58/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.59/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.60/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.61/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.62/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.63/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.64/321GINERNETGINERNETASSIGNED PAMar 13, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.65/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.66/321GINERNETGINERNETASSIGNED PAMar 13, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.67/321GINERNETGINERNETASSIGNED PAMar 13, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.68/321GINERNETGINERNETASSIGNED PAMar 13, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.69/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.70/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.71/321GINERNETGINERNETASSIGNED PAMar 13, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.72/321GINERNETGINERNETASSIGNED PADec 14, 2023abuse@ginernet.com
via GINERNET
└ 185.47.131.73/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.74/321GINERNETGINERNETASSIGNED PADec 16, 2023abuse@ginernet.com
via GINERNET
└ 185.47.131.75/321GINERNETGINERNETASSIGNED PADec 14, 2023abuse@ginernet.com
via GINERNET
└ 185.47.131.76/321GINERNETGINERNETASSIGNED PADec 16, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.77/321GINERNETGINERNETASSIGNED PAMar 14, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.78/321GINERNETGINERNETASSIGNED PADec 16, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.79/321GINERNETGINERNETASSIGNED PAApr 14, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.80/321GINERNETGINERNETASSIGNED PAFeb 25, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.81/321GINERNETGINERNETASSIGNED PAMar 14, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.82/321GINERNETGINERNETASSIGNED PAMar 24, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.83/321GINERNETGINERNETASSIGNED PAMar 15, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.84/321GINERNETGINERNETASSIGNED PAApr 19, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.85/321GINERNETGINERNETASSIGNED PAFeb 27, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.86/321GINERNETGINERNETASSIGNED PAMar 15, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.87/321GINERNETGINERNETASSIGNED PAMar 15, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.88/321GINERNETGINERNETASSIGNED PAMar 24, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.89/321GINERNETGINERNETASSIGNED PAApr 14, 2025abuse@ginernet.com
via GINERNET
└ 185.47.131.90/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.91/321GINERNETGINERNETASSIGNED PAMar 3, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.92/321GINERNETGINERNETASSIGNED PAMar 4, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.93/321GINERNETGINERNETASSIGNED PAApr 7, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.94/321GINERNETGINERNETASSIGNED PAMar 5, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.95/321GINERNETGINERNETASSIGNED PAJan 12, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.96/321GINERNETGINERNETASSIGNED PAMay 12, 2021abuse@ginernet.com
via GINERNET
└ 185.47.131.97/321GINERNETGINERNETASSIGNED PAMar 18, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.98/321GINERNETGINERNETASSIGNED PAMay 23, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.99/321GINERNETGINERNETASSIGNED PANov 18, 2023abuse@ginernet.com
via GINERNET
└ 185.47.131.100/321GINERNETGINERNETASSIGNED PAJul 3, 2025abuse@ginernet.com
via GINERNET
└ 185.47.131.101/321GINERNETGINERNETASSIGNED PAApr 5, 2022abuse@ginernet.com
via GINERNET
└ 185.47.131.102/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.103/321GINERNETGINERNETASSIGNED PAMar 16, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.104/321GINERNETGINERNETASSIGNED PAMar 18, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.105/321GINERNETGINERNETASSIGNED PAMar 18, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.106/321GINERNETGINERNETASSIGNED PAMar 19, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.107/321GINERNETGINERNETASSIGNED PAMar 20, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.108/321GINERNETGINERNETASSIGNED PAMar 21, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.109/321GINERNETGINERNETASSIGNED PAAug 7, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.110/321GINERNETGINERNETASSIGNED PADec 10, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.111/321GINERNETGINERNETASSIGNED PAMar 22, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.112/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.113/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.114/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.115/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.116/321GINERNETGINERNETASSIGNED PAMar 25, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.117/321GINERNETGINERNETASSIGNED PAMar 25, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.118/321GINERNETGINERNETASSIGNED PAMar 22, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.119/321GINERNETGINERNETASSIGNED PAMar 23, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.120/321GINERNETGINERNETASSIGNED PAApr 1, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.121/321GINERNETGINERNETASSIGNED PAMar 24, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.122/321GINERNETGINERNETASSIGNED PAMar 24, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.123/321GINERNETGINERNETASSIGNED PAMar 25, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.124/321GINERNETGINERNETASSIGNED PAApr 2, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.125/321GINERNETGINERNETASSIGNED PAApr 3, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.126/321GINERNETGINERNETASSIGNED PAApr 8, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.127/321GINERNETGINERNETASSIGNED PAMar 26, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.128/321GINERNETGINERNETASSIGNED PAMar 26, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.129/321GINERNETGINERNETASSIGNED PAMay 6, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.130/321GINERNETGINERNETASSIGNED PADec 2, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.131/321GINERNETGINERNETASSIGNED PAApr 8, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.132/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.133/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.134/321GINERNETGINERNETASSIGNED PAApr 12, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.135/321GINERNETGINERNETASSIGNED PAApr 13, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.136/321GINERNETGINERNETASSIGNED PAApr 14, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.137/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.138/321GINERNETGINERNETASSIGNED PAApr 15, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.139/321GINERNETGINERNETASSIGNED PAApr 16, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.140/321GINERNETGINERNETASSIGNED PASep 4, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.141/321GINERNETGINERNETASSIGNED PAApr 16, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.142/321GINERNETGINERNETASSIGNED PAApr 10, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.143/321GINERNETGINERNETASSIGNED PAApr 28, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.144/321GINERNETGINERNETASSIGNED PAApr 1, 2022abuse@ginernet.com
via GINERNET
└ 185.47.131.145/321GINERNETGINERNETASSIGNED PAApr 17, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.146/321GINERNETGINERNETASSIGNED PAApr 14, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.147/321GINERNETGINERNETASSIGNED PAApr 17, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.148/321GINERNETGINERNETASSIGNED PAApr 14, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.149/321GINERNETGINERNETASSIGNED PAApr 14, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.150/321GINERNETGINERNETASSIGNED PAApr 17, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.151/321GINERNETGINERNETASSIGNED PAApr 19, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.152/321GINERNETGINERNETASSIGNED PAApr 19, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.153/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.154/321GINERNETGINERNETASSIGNED PAAug 10, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.155/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.156/321GINERNETGINERNETASSIGNED PAMay 6, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.157/321GINERNETGINERNETASSIGNED PAApr 16, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.158/321GINERNETGINERNETASSIGNED PAApr 22, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.159/321GINERNETGINERNETASSIGNED PAApr 22, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.160/321GINERNETGINERNETASSIGNED PAMay 7, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.161/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.162/321GINERNETGINERNETASSIGNED PAMay 6, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.163/321GINERNETGINERNETASSIGNED PAApr 22, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.164/321GINERNETGINERNETASSIGNED PASep 7, 2022abuse@ginernet.com
via GINERNET
└ 185.47.131.165/321GINERNETGINERNETASSIGNED PAMay 7, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.166/321GINERNETGINERNETASSIGNED PADec 12, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.167/321GINERNETGINERNETASSIGNED PAApr 23, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.168/321GINERNETGINERNETASSIGNED PAJun 18, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.169/321GINERNETGINERNETASSIGNED PAJun 18, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.170/321GINERNETGINERNETASSIGNED PAApr 23, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.171/321GINERNETGINERNETASSIGNED PAJun 18, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.172/321GINERNETGINERNETASSIGNED PASep 25, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.173/321GINERNETGINERNETASSIGNED PAJun 18, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.174/321GINERNETGINERNETASSIGNED PAJun 18, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.175/321GINERNETGINERNETASSIGNED PAJun 18, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.176/321GINERNETGINERNETASSIGNED PAApr 23, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.177/321GINERNETGINERNETASSIGNED PAMay 11, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.178/321GINERNETGINERNETASSIGNED PAApr 24, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.179/321GINERNETGINERNETASSIGNED PAApr 24, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.180/321GINERNETGINERNETASSIGNED PASep 26, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.181/321GINERNETGINERNETASSIGNED PAMay 12, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.182/321GINERNETGINERNETASSIGNED PAApr 24, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.183/321GINERNETGINERNETASSIGNED PAOct 6, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.184/321GINERNETGINERNETASSIGNED PAMay 12, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.185/321GINERNETGINERNETASSIGNED PAMay 14, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.186/321GINERNETGINERNETASSIGNED PAOct 7, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.187/321EBTABLESJNGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.188/321GINERNETGINERNETASSIGNED PANov 3, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.189/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.190/321GINERNETGINERNETASSIGNED PAAug 12, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.191/321GINERNETGINERNETASSIGNED PAMay 19, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.192/321GINERNETGINERNETASSIGNED PAApr 27, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.193/321GINERNETGINERNETASSIGNED PAAug 13, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.194/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.195/321GINERNETGINERNETASSIGNED PANov 4, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.196/321GINERNETGINERNETASSIGNED PAMay 20, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.197/321GINERNETGINERNETASSIGNED PAMay 20, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.198/321GINERNETGINERNETASSIGNED PAMay 22, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.199/321GINERNETGINERNETASSIGNED PAOct 18, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.200/321GINERNETGINERNETASSIGNED PAMay 22, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.201/321GINERNETGINERNETASSIGNED PAMay 22, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.202/321GINERNETGINERNETASSIGNED PAOct 18, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.203/321GINERNETGINERNETASSIGNED PAMay 18, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.204/321GINERNETGINERNETASSIGNED PAOct 23, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.205/321GINERNETGINERNETASSIGNED PAOct 23, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.206/321GINERNETGINERNETASSIGNED PAOct 23, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.207/321GINERNETGINERNETASSIGNED PAOct 23, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.208/321GINERNETGINERNETASSIGNED PAOct 18, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.209/321GINERNETGINERNETASSIGNED PAMay 19, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.210/321GINERNETGINERNETASSIGNED PAOct 18, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.211/321GINERNETGINERNETASSIGNED PASep 19, 2022abuse@ginernet.com
via GINERNET
└ 185.47.131.212/321GINERNETGINERNETASSIGNED PAMay 19, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.213/321GINERNETGINERNETASSIGNED PAJun 3, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.214/321GINERNETGINERNETASSIGNED PAOct 19, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.215/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.216/321GINERNETGINERNETASSIGNED PAJun 3, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.217/321GINERNETGINERNETASSIGNED PAMay 21, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.218/321GINERNETGINERNETASSIGNED PADec 19, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.219/321GINERNETGINERNETASSIGNED PAMay 21, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.220/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.131.221/321GINERNETGINERNETASSIGNED PAJun 25, 2025abuse@ginernet.com
via GINERNET
└ 185.47.131.222/321GINERNETGINERNETASSIGNED PAJun 17, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.223/321GINERNETGINERNETASSIGNED PAJun 17, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.224/321GINERNETGINERNETASSIGNED PAMay 22, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.225/321GINERNETGINERNETASSIGNED PAMay 22, 2024abuse@ginernet.com
via GINERNET
└ 185.47.131.226/321GINERNETGINERNETASSIGNED PAJun 25, 2025abuse@ginernet.com
via GINERNET
└ 185.47.131.227/321GINERNETGINERNETASSIGNED PAOct 9, 2020abuse@ginernet.com
via GINERNET
└ 185.47.131.228/321GINERNETGINERNETASSIGNED PAMay 22, 2024abuse@ginernet.com
via GINERNET
← Previous1–200 of 216 · page 1 of 2Next →

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Registry

Holder

Organization
Ginernet S.L.
Handle
ORG-JMG1-RIPE
Range
185.47.128.0/22
Registration type
ALLOCATED PA
Record created
Feb 12, 2014
Reallocated to
GINERNET
Reallocated range
185.47.131.0/24
Reallocation type
LIR-PARTITIONED PA
Reallocated
Oct 27, 2018
Origin network

AS59432

ES
Name
Ginernet S.L.
Type
Hosting
Registered
Jul 10, 2012
Domain
ginernet.com
Website
ginernet.com
Spamhaus ASN-DROP
not listed