Data as of Nov 18, 2026

185.47.128.0/22

2 residential-proxy exits · 30 days

Ginernet S.L.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting

Residential-proxy exits

Proxy exits
2
0.20% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
9
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

46 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.47.128.0/2401
185.47.131.0/2401

Proxy providers listing exits

  • Ake.net
  • EnigmaProxy
  • FastProxy
  • LudaxProxy
  • NovaProxy
  • Proxiware
  • ProxyEmpire
  • VantageProxies
  • ZENPROXY_LITE

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
185.47.128.0/24
since Jul 2014
AS59432Hosting1Ginernet S.L.
via GINERNET
185.47.129.0/24
since Feb 2015
AS59432HostingGinernet S.L.
via GINERNET
185.47.130.0/24
since Feb 2015
AS59432HostingGinernet S.L.
via GINERNET AntiDDoS - Voxility DDoS Protected IPs
185.47.131.0/24
since Mar 2015
AS59432Hosting1Ginernet S.L.
via GINERNET

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.128.233/32
under 185.47.128.0/24
1GINERNETGINERNETASSIGNED PASep 25, 2024abuse@ginernet.com
via 185.47.128.0/24
185.47.128.234/32
under 185.47.128.0/24
1GINERNETGINERNETASSIGNED PAOct 21, 2022abuse@ginernet.com
via 185.47.128.0/24
185.47.128.235/32
under 185.47.128.0/24
1GINERNETGINERNETASSIGNED PASep 6, 2021abuse@ginernet.com
via 185.47.128.0/24
185.47.128.236/32
under 185.47.128.0/24
1GINERNETGINERNETASSIGNED PAJun 6, 2023abuse@ginernet.com
via 185.47.128.0/24
185.47.128.237/32
under 185.47.128.0/24
1GINERNETGINERNETASSIGNED PAApr 28, 2021abuse@ginernet.com
via 185.47.128.0/24
185.47.128.238/32
under 185.47.128.0/24
1GINERNETGINERNETASSIGNED PAJan 10, 2021abuse@ginernet.com
via 185.47.128.0/24
185.47.128.239/32
under 185.47.128.0/24
1GINERNETGINERNETASSIGNED PAAug 23, 2024abuse@ginernet.com
via 185.47.128.0/24
185.47.128.240/32
under 185.47.128.0/24
1JAVIHNETUPSTREAM MadridASSIGNED PAApr 29, 2021abuse@ginernet.com
via 185.47.128.0/24
185.47.128.241/32
under 185.47.128.0/24
1GINERNETGINERNETASSIGNED PAApr 25, 2025abuse@ginernet.com
via 185.47.128.0/24
185.47.128.242/32
under 185.47.128.0/24
1GINERNETGINERNETASSIGNED PASep 22, 2024abuse@ginernet.com
via 185.47.128.0/24
185.47.128.244/32
under 185.47.128.0/24
1GINERNETGINERNETASSIGNED PAApr 29, 2021abuse@ginernet.com
via 185.47.128.0/24
185.47.128.245/32
under 185.47.128.0/24
1GINERNETGINERNETASSIGNED PAOct 21, 2022abuse@ginernet.com
via 185.47.128.0/24
185.47.128.246/32
under 185.47.128.0/24
1GINERNETGINERNETASSIGNED PAApr 30, 2021abuse@ginernet.com
via 185.47.128.0/24
185.47.128.247/32
under 185.47.128.0/24
1GINERNETGINERNETASSIGNED PAMay 4, 2021abuse@ginernet.com
via 185.47.128.0/24
185.47.128.248/29
under 185.47.128.0/24
8GINERNETGINERNETASSIGNED PAApr 12, 2023abuse@ginernet.com
via 185.47.128.0/24
└ 185.47.129.0/24256GINERNETGINERNETLIR-PARTITIONED PAOct 27, 2018abuse@ginernet.com
via ES-GINERNET-20140212
└ 185.47.129.0/2816GINERNETGINERNETASSIGNED PAFeb 5, 2020abuse@ginernet.com
via GINERNET
└ 185.47.129.16/298GINERNETGINERNETASSIGNED PAFeb 5, 2020abuse@ginernet.com
via GINERNET
└ 185.47.129.25/321GINERNETGINERNETASSIGNED PAFeb 5, 2020abuse@ginernet.com
via GINERNET
└ 185.47.129.28/321GINERNETGINERNETASSIGNED PAFeb 5, 2020abuse@ginernet.com
via GINERNET
└ 185.47.129.33/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.34/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.35/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.37/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.38/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.39/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.40/321GINERNETGINERNETASSIGNED PAOct 1, 2022abuse@ginernet.com
via GINERNET
└ 185.47.129.41/321GINERNETGINERNETASSIGNED PAOct 1, 2022abuse@ginernet.com
via GINERNET
└ 185.47.129.42/321GINERNETGINERNETASSIGNED PAOct 1, 2022abuse@ginernet.com
via GINERNET
└ 185.47.129.43/321GINERNETGINERNETASSIGNED PAOct 1, 2022abuse@ginernet.com
via GINERNET
└ 185.47.129.44/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.47/321GINERNETGINERNETASSIGNED PADec 12, 2024abuse@ginernet.com
via GINERNET
└ 185.47.129.50/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.51/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.52/321GINERNETGINERNETASSIGNED PANov 3, 2022abuse@ginernet.com
via GINERNET
└ 185.47.129.53/321GINERNETGINERNETASSIGNED PANov 3, 2022abuse@ginernet.com
via GINERNET
└ 185.47.129.54/321GINERNETGINERNETASSIGNED PANov 3, 2022abuse@ginernet.com
via GINERNET
└ 185.47.129.55/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.58/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.62/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.67/321GINERNETGINERNETASSIGNED PAJul 31, 2025abuse@ginernet.com
via GINERNET
└ 185.47.129.68/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.72/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.73/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.74/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.75/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.76/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.77/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.78/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.79/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.80/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.81/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.82/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.83/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.84/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.85/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.86/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.87/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.92/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.93/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.94/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.97/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.99/321GINERNETGINERNETASSIGNED PANov 14, 2024abuse@ginernet.com
via GINERNET
└ 185.47.129.100/321GINERNETGINERNETASSIGNED PASep 17, 2024abuse@ginernet.com
via GINERNET
└ 185.47.129.101/321GINERNETGINERNETASSIGNED PASep 17, 2024abuse@ginernet.com
via GINERNET
└ 185.47.129.102/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.103/321GINERNETGINERNETASSIGNED PASep 17, 2024abuse@ginernet.com
via GINERNET
└ 185.47.129.104/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.105/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.106/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.108/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.109/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.110/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.111/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.112/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.114/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.116/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.117/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.121/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.122/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.124/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.126/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.128/321GINERNETGINERNETASSIGNED PASep 1, 2022abuse@ginernet.com
via GINERNET
└ 185.47.129.129/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.130/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.131/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.132/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.133/321GINERNETGINERNETASSIGNED PASep 1, 2022abuse@ginernet.com
via GINERNET
└ 185.47.129.134/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.135/321GINERNETGINERNETASSIGNED PASep 1, 2022abuse@ginernet.com
via GINERNET
└ 185.47.129.136/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.137/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.138/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.139/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.140/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.141/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.142/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 185.47.129.143/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.144/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.145/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.146/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.148/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.150/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.154/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.155/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.156/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.157/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.158/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.159/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.160/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.162/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.163/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.164/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.166/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.167/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.168/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.169/321GINERNETGINERNETASSIGNED PAOct 13, 2022abuse@ginernet.com
via GINERNET
└ 185.47.129.170/321GINERNETGINERNETASSIGNED PAOct 13, 2022abuse@ginernet.com
via GINERNET
└ 185.47.129.171/321GINERNETGINERNETASSIGNED PAOct 13, 2022abuse@ginernet.com
via GINERNET
└ 185.47.129.173/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.174/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.175/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.179/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.182/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.186/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.188/321GINERNETGINERNETASSIGNED PAAug 31, 2023abuse@ginernet.com
via GINERNET
└ 185.47.129.189/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.190/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.191/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.194/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.195/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 185.47.129.196/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 185.47.129.197/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 185.47.129.198/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.199/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 185.47.129.200/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 185.47.129.201/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.202/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 185.47.129.203/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 185.47.129.205/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.208/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.209/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.210/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.211/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.212/321GINERNETGINERNETASSIGNED PAOct 3, 2022abuse@ginernet.com
via GINERNET
└ 185.47.129.213/321GINERNETGINERNETASSIGNED PASep 11, 2024abuse@ginernet.com
via GINERNET
└ 185.47.129.214/321GINERNETGINERNETASSIGNED PAOct 3, 2022abuse@ginernet.com
via GINERNET
└ 185.47.129.215/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.216/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.217/321GINERNETGINERNETASSIGNED PAOct 3, 2022abuse@ginernet.com
via GINERNET
└ 185.47.129.218/321GINERNETGINERNETASSIGNED PAOct 3, 2022abuse@ginernet.com
via GINERNET
└ 185.47.129.219/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.220/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.221/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.222/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.223/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.228/321GINERNETGINERNETASSIGNED PAOct 15, 2022abuse@ginernet.com
via GINERNET
└ 185.47.129.229/321GINERNETGINERNETASSIGNED PAOct 15, 2022abuse@ginernet.com
via GINERNET
└ 185.47.129.231/321GINERNETGINERNETASSIGNED PAOct 15, 2022abuse@ginernet.com
via GINERNET
└ 185.47.129.234/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.236/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.237/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.238/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.239/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.240/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.242/321GINERNETGINERNETASSIGNED PAJul 17, 2024abuse@ginernet.com
via GINERNET
└ 185.47.129.244/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 185.47.129.246/321GINERNETGINERNETASSIGNED PAMay 7, 2025abuse@ginernet.com
via GINERNET
└ 185.47.129.250/312GINERNETGINERNETASSIGNED PAFeb 5, 2020abuse@ginernet.com
via GINERNET
└ 185.47.129.252/304GINERNETGINERNETASSIGNED PAFeb 5, 2020abuse@ginernet.com
via GINERNET
└ 185.47.130.0/24256GINERNET_AntiDDoSGINERNET AntiDDoS - Voxility DDoS Protected IPsLIR-PARTITIONED PAOct 27, 2018abuse@ginernet.com
via ES-GINERNET-20140212
└ 185.47.130.32/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PAMar 10, 2022abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.33/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PAMar 23, 2023abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.34/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PAAug 30, 2019abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.35/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PAAug 30, 2019abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.36/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PASep 3, 2019abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.37/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PASep 3, 2019abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.38/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PAJan 10, 2021abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.39/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PAJun 24, 2020abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.40/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PASep 2, 2022abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.41/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PAMar 10, 2022abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.42/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PASep 4, 2019abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.43/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PASep 10, 2019abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.44/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PASep 30, 2022abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.45/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PASep 11, 2019abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.46/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PAOct 13, 2021abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.47/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PAJun 20, 2025abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.48/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PAFeb 9, 2022abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.49/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PAJun 27, 2025abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.50/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PAOct 9, 2024abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.51/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PAOct 23, 2022abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.52/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PAAug 15, 2023abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.53/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PAMar 4, 2025abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.54/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PAMay 3, 2022abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.55/321GOONGOONASSIGNED PAMay 5, 2025abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.56/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PAJul 12, 2025abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.57/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PANov 9, 2024abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.58/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PAApr 14, 2025abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.59/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PANov 9, 2024abuse@ginernet.com
via GINERNET_AntiDDoS
└ 185.47.130.60/321GINERNET_AntiDDoSGINERNET AntiDDoS - DDoS Protected IPsASSIGNED PAMay 1, 2023abuse@ginernet.com
via GINERNET_AntiDDoS
← Previous201–400 of 674 · page 2 of 4Next →

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

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