Data as of Nov 8, 2026

5.134.118.0/24

1 residential-proxy exit · 30 days

Ginernet S.L.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

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

Exits seen per day

3 observations

Proxy providers listing exits

  • GloryCloud
  • KindProxy
  • PuraRoute

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
5.134.112.0/21
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
5.134.112.0/212,048ES-GINERNET-20120710Ginernet S.L. (ORG-JMG1-RIPE) · ESALLOCATED PAJul 10, 2012abuse@ginernet.com
└ 5.134.118.0/24256GINERNETGINERNETLIR-PARTITIONED PAOct 27, 2018abuse@ginernet.com
via ES-GINERNET-20120710
└ 5.134.118.0/2732GINERNETGINERNETASSIGNED PAJun 18, 2020abuse@ginernet.com
via GINERNET
└ 5.134.118.32/304GINERNETGINERNETASSIGNED PASep 1, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.36/321GINERNETGINERNETASSIGNED PAAug 15, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.37/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.118.38/321GINERNETGINERNETASSIGNED PAJan 10, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.39/321GINERNETGINERNETASSIGNED PAMay 21, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.40/312GINERNETGINERNETASSIGNED PAMay 17, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.42/321GINERNETGINERNETASSIGNED PAMay 17, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.43/321GINERNETGINERNETASSIGNED PAMay 17, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.44/321GINERNETGINERNETASSIGNED PAMay 21, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.45/321GINERNETGINERNETASSIGNED PAMay 21, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.46/321GINERNETGINERNETASSIGNED PAMay 21, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.47/321GINERNETGINERNETASSIGNED PAOct 25, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.48/321GINERNETGINERNETASSIGNED PAAug 21, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.49/321GINERNETGINERNETASSIGNED PAAug 22, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.50/321GINERNETGINERNETASSIGNED PAMay 22, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.51/321GINERNETGINERNETASSIGNED PAMay 20, 2024abuse@ginernet.com
via GINERNET
└ 5.134.118.52/321GINERNETGINERNETASSIGNED PAAug 22, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.53/321GINERNETGINERNETASSIGNED PAMay 22, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.54/321GINERNETGINERNETASSIGNED PAAug 23, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.55/321GINERNETGINERNETASSIGNED PAFeb 8, 2024abuse@ginernet.com
via GINERNET
└ 5.134.118.56/312GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.58/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.59/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.60/321GINERNETGINERNETASSIGNED PASep 16, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.61/321GINERNETGINERNETASSIGNED PAAug 24, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.62/321GINERNETGINERNETASSIGNED PASep 29, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.63/321GINERNETGINERNETASSIGNED PASep 20, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.64/321GINERNETGINERNETASSIGNED PAAug 30, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.65/321GINERNETGINERNETASSIGNED PAAug 30, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.67/321GINERNETGINERNETASSIGNED PASep 21, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.68/321GINERNETGINERNETASSIGNED PAAug 31, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.69/321GINERNETGINERNETASSIGNED PAMay 10, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.70/321GINERNETGINERNETASSIGNED PAAug 31, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.71/321GINERNETGINERNETASSIGNED PAMay 10, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.72/312GINERNETGINERNETASSIGNED PAAug 3, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.74/321GINERNETGINERNETASSIGNED PAAug 3, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.75/321GINERNETGINERNETASSIGNED PAAug 3, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.76/321GINERNETGINERNETASSIGNED PASep 24, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.77/321GINERNETGINERNETASSIGNED PASep 4, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.78/321GINERNETGINERNETASSIGNED PASep 4, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.79/321GINERNETGINERNETASSIGNED PASep 4, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.80/312GINERNETGINERNETASSIGNED PANov 9, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.82/321GINERNETGINERNETASSIGNED PANov 9, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.83/321GINERNETGINERNETASSIGNED PANov 9, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.84/312GINERNETGINERNETASSIGNED PAAug 16, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.86/321GINERNETGINERNETASSIGNED PAAug 16, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.87/321GINERNETGINERNETASSIGNED PAAug 16, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.88/321GINERNETGINERNETASSIGNED PAJul 31, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.89/321GINERNETGINERNETASSIGNED PAOct 19, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.90/321GINERNETGINERNETASSIGNED PASep 7, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.91/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.118.92/312GINERNETGINERNETASSIGNED PAMay 27, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.94/321GINERNETGINERNETASSIGNED PAMay 27, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.95/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.118.96/321GINERNETGINERNETASSIGNED PANov 15, 2024abuse@ginernet.com
via GINERNET
└ 5.134.118.97/321GINERNETGINERNETASSIGNED PASep 5, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.98/321GINERNETGINERNETASSIGNED PASep 5, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.99/321GINERNETGINERNETASSIGNED PAMay 10, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.100/312GINERNETGINERNETASSIGNED PAMay 24, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.102/321GINERNETGINERNETASSIGNED PAJul 13, 2024abuse@ginernet.com
via GINERNET
└ 5.134.118.103/321GINERNETGINERNETASSIGNED PAMay 24, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.104/321GINERNETGINERNETASSIGNED PAMay 11, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.105/321GINERNETGINERNETASSIGNED PAMay 11, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.106/321GINERNETGINERNETASSIGNED PAFeb 4, 2025abuse@ginernet.com
via GINERNET
└ 5.134.118.107/321GINERNETGINERNETASSIGNED PAOct 3, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.108/321GINERNETGINERNETASSIGNED PAFeb 10, 2024abuse@ginernet.com
via GINERNET
└ 5.134.118.109/321GINERNETGINERNETASSIGNED PAJun 8, 2024abuse@ginernet.com
via GINERNET
└ 5.134.118.110/321GINERNETGINERNETASSIGNED PAMay 18, 2025abuse@ginernet.com
via GINERNET
└ 5.134.118.111/321GINERNETGINERNETASSIGNED PAOct 5, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.112/321GINERNETGINERNETASSIGNED PAOct 6, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.113/321GINERNETGINERNETASSIGNED PAOct 19, 2024abuse@ginernet.com
via GINERNET
└ 5.134.118.114/321GINERNETGINERNETASSIGNED PAOct 7, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.115/321GINERNETGINERNETASSIGNED PASep 23, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.116/321GINERNETGINERNETASSIGNED PASep 23, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.117/321GINERNETGINERNETASSIGNED PAOct 7, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.118/321GINERNETGINERNETASSIGNED PAMar 16, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.119/321RELEVAIRELEVAIASSIGNED PAOct 7, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.120/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.118.121/321GINERNETGINERNETASSIGNED PASep 24, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.122/321GINERNETGINERNETASSIGNED PAOct 8, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.123/321GINERNETGINERNETASSIGNED PASep 25, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.124/321GINERNETGINERNETASSIGNED PASep 25, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.125/321GINERNETGINERNETASSIGNED PAOct 8, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.126/321GINERNETGINERNETASSIGNED PAOct 8, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.127/321GINERNETGINERNETASSIGNED PAMay 15, 2025abuse@ginernet.com
via GINERNET
└ 5.134.118.128/321GINERNETGINERNETASSIGNED PAOct 8, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.129/321GINERNETGINERNETASSIGNED PAOct 8, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.130/321GINERNETGINERNETASSIGNED PAOct 8, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.131/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.118.132/321GINERNETGINERNETASSIGNED PASep 26, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.133/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.118.134/321GINERNETGINERNETASSIGNED PAOct 8, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.135/321GINERNETGINERNETASSIGNED PAJun 12, 2024abuse@ginernet.com
via GINERNET
└ 5.134.118.136/321GINERNETGINERNETASSIGNED PAOct 23, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.137/321GINERNETGINERNETASSIGNED PAJan 10, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.138/321GINERNETGINERNETASSIGNED PAOct 24, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.139/321GINERNETGINERNETASSIGNED PAOct 24, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.140/321GINERNETGINERNETASSIGNED PANov 1, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.141/321GINERNETGINERNETASSIGNED PAMay 24, 2025abuse@ginernet.com
via GINERNET
└ 5.134.118.142/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.118.143/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.118.144/321GINERNETGINERNETASSIGNED PADec 7, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.145/321GINERNETGINERNETASSIGNED PADec 7, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.146/321GINERNETGINERNETASSIGNED PADec 7, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.147/321GINERNETGINERNETASSIGNED PADec 7, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.148/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.118.149/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.118.150/321RELEVAIRELEVAIASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.118.151/321GINERNETGINERNETASSIGNED PAMay 19, 2025abuse@ginernet.com
via GINERNET
└ 5.134.118.152/321GINERNETGINERNETASSIGNED PANov 6, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.153/321GINERNETGINERNETASSIGNED PANov 6, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.154/321GINERNETGINERNETASSIGNED PADec 10, 2024abuse@ginernet.com
via GINERNET
└ 5.134.118.155/321GINERNETGINERNETASSIGNED PAJul 2, 2025abuse@ginernet.com
via GINERNET
└ 5.134.118.156/321GINERNETGINERNETASSIGNED PANov 6, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.157/321GINERNETGINERNETASSIGNED PANov 6, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.158/321GINERNETGINERNETASSIGNED PANov 6, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.159/321GINERNETGINERNETASSIGNED PANov 7, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.160/321GINERNETGINERNETASSIGNED PAOct 26, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.161/321GINERNETGINERNETASSIGNED PAMar 20, 2025abuse@ginernet.com
via GINERNET
└ 5.134.118.162/321GINERNETGINERNETASSIGNED PAOct 26, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.163/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.118.164/321GINERNETGINERNETASSIGNED PAOct 26, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.165/321GINERNETGINERNETASSIGNED PAOct 26, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.166/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.118.167/321GINERNETGINERNETASSIGNED PAOct 26, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.168/321GINERNETGINERNETASSIGNED PANov 20, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.169/321GINERNETGINERNETASSIGNED PAFeb 5, 2025abuse@ginernet.com
via GINERNET
└ 5.134.118.170/321GINERNETGINERNETASSIGNED PANov 20, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.171/321GINERNETGINERNETASSIGNED PANov 21, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.172/321GINERNETGINERNETASSIGNED PAOct 9, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.173/321GINERNETGINERNETASSIGNED PAOct 9, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.174/321GINERNETGINERNETASSIGNED PAOct 9, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.175/321GINERNETGINERNETASSIGNED PADec 14, 2024abuse@ginernet.com
via GINERNET
└ 5.134.118.176/321GINERNETGINERNETASSIGNED PAOct 8, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.177/321GINERNETGINERNETASSIGNED PANov 24, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.178/321GINERNETGINERNETASSIGNED PAOct 8, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.179/321GINERNETGINERNETASSIGNED PAOct 8, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.180/321GINERNETGINERNETASSIGNED PAOct 8, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.181/321GINERNETGINERNETASSIGNED PANov 24, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.182/321GINERNETGINERNETASSIGNED PANov 25, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.183/321GINERNETGINERNETASSIGNED PANov 25, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.184/321GINERNETGINERNETASSIGNED PAFeb 16, 2024abuse@ginernet.com
via GINERNET
└ 5.134.118.185/321GINERNETGINERNETASSIGNED PAOct 8, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.186/321GINERNETGINERNETASSIGNED PAOct 8, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.187/321GINERNETGINERNETASSIGNED PAOct 8, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.188/321GINERNETGINERNETASSIGNED PAFeb 25, 2025abuse@ginernet.com
via GINERNET
└ 5.134.118.189/321GINERNETGINERNETASSIGNED PANov 25, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.190/321GINERNETGINERNETASSIGNED PAOct 8, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.191/321GINERNETGINERNETASSIGNED PAOct 8, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.192/321GINERNETGINERNETASSIGNED PAOct 26, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.193/321GINERNETGINERNETASSIGNED PAOct 26, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.194/321GINERNETGINERNETASSIGNED PAOct 26, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.195/321GINERNETGINERNETASSIGNED PASep 12, 2024abuse@ginernet.com
via GINERNET
└ 5.134.118.196/321GINERNETGINERNETASSIGNED PAOct 26, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.197/321GINERNETGINERNETASSIGNED PAOct 26, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.198/321GINERNETGINERNETASSIGNED PAOct 26, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.199/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.118.200/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.118.201/321GINERNETGINERNETASSIGNED PANov 29, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.202/321GINERNETGINERNETASSIGNED PANov 29, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.203/321GINERNETGINERNETASSIGNED PAJul 15, 2024abuse@ginernet.com
via GINERNET
└ 5.134.118.204/321GINERNETGINERNETASSIGNED PAOct 8, 2024abuse@ginernet.com
via GINERNET
└ 5.134.118.205/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.118.206/321GINERNETGINERNETASSIGNED PAJun 3, 2025abuse@ginernet.com
via GINERNET
└ 5.134.118.207/321GINERNETGINERNETASSIGNED PADec 1, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.208/321GINERNETGINERNETASSIGNED PAFeb 27, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.209/321GINERNETGINERNETASSIGNED PAFeb 27, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.210/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.118.211/321GINERNETGINERNETASSIGNED PADec 4, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.212/321GINERNETGINERNETASSIGNED PADec 4, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.213/321GINERNETGINERNETASSIGNED PADec 4, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.214/321GINERNETGINERNETASSIGNED PADec 4, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.215/321GINERNETGINERNETASSIGNED PADec 4, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.216/321GINERNETGINERNETASSIGNED PADec 4, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.217/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.118.218/321GINERNETGINERNETASSIGNED PADec 4, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.219/321GINERNETGINERNETASSIGNED PAAug 6, 2025abuse@ginernet.com
via GINERNET
└ 5.134.118.220/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.118.221/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.118.222/321GINERNETGINERNETASSIGNED PAFeb 18, 2024abuse@ginernet.com
via GINERNET
└ 5.134.118.223/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.118.224/321GINERNETGINERNETASSIGNED PAOct 13, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.225/321GINERNETGINERNETASSIGNED PAMar 21, 2024abuse@ginernet.com
via GINERNET
└ 5.134.118.226/321GINERNETGINERNETASSIGNED PAOct 13, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.227/321GINERNETGINERNETASSIGNED PAOct 13, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.228/321GINERNETGINERNETASSIGNED PAOct 13, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.229/321GINERNETGINERNETASSIGNED PANov 13, 2024abuse@ginernet.com
via GINERNET
└ 5.134.118.230/321GINERNETGINERNETASSIGNED PAFeb 10, 2024abuse@ginernet.com
via GINERNET
└ 5.134.118.231/321GINERNETGINERNETASSIGNED PAOct 13, 2022abuse@ginernet.com
via GINERNET
└ 5.134.118.232/321GINERNETGINERNETASSIGNED PADec 8, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.233/321GINERNETGINERNETASSIGNED PADec 8, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.234/321GINERNETGINERNETASSIGNED PAFeb 6, 2025abuse@ginernet.com
via GINERNET
└ 5.134.118.235/321GINERNETGINERNETASSIGNED PAMay 16, 2025abuse@ginernet.com
via GINERNET
└ 5.134.118.236/321GINERNETGINERNETASSIGNED PADec 21, 2023abuse@ginernet.com
via GINERNET
└ 5.134.118.237/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.118.238/321GINERNETGINERNETASSIGNED PAJan 10, 2021abuse@ginernet.com
via GINERNET
└ 5.134.118.239/321GINERNETGINERNETASSIGNED PAJan 8, 2024abuse@ginernet.com
via GINERNET
└ 5.134.118.240/321GINERNETGINERNETASSIGNED PAJan 25, 2024abuse@ginernet.com
via GINERNET
└ 5.134.118.241/321GINERNETGINERNETASSIGNED PAJan 25, 2024abuse@ginernet.com
via GINERNET
← Previous1–200 of 209 · 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
5.134.112.0/21
Registration type
ALLOCATED PA
Record created
Jul 10, 2012
Reallocated to
GINERNET
Reallocated range
5.134.118.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