Data as of Nov 7, 2026

5.134.119.0/24

No anonymizer space · no proxy exits in 30 days

Ginernet S.L.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting

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.119.0/24256GINERNETGINERNETLIR-PARTITIONED PAFeb 1, 2020abuse@ginernet.com
via ES-GINERNET-20120710
└ 5.134.119.0/2732GINERNETGINERNETASSIGNED PAMar 17, 2023abuse@ginernet.com
via GINERNET
└ 5.134.119.32/321GINERNETGINERNETASSIGNED PAMay 11, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.33/321GINERNETGINERNETASSIGNED PAJan 28, 2024abuse@ginernet.com
via GINERNET
└ 5.134.119.34/321GINERNETGINERNETASSIGNED PAMar 10, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.35/321GINERNETGINERNETASSIGNED PADec 6, 2018abuse@ginernet.com
via GINERNET
└ 5.134.119.36/321GINERNETGINERNETASSIGNED PAJul 19, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.37/321GINERNETGINERNETASSIGNED PAFeb 11, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.38/321GINERNETGINERNETASSIGNED PAJun 13, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.39/321GINERNETGINERNETASSIGNED PAMar 5, 2024abuse@ginernet.com
via GINERNET
└ 5.134.119.40/321GINERNETGINERNETASSIGNED PAJun 29, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.41/321GINERNETGINERNETASSIGNED PAApr 1, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.42/321GINERNETGINERNETASSIGNED PADec 20, 2018abuse@ginernet.com
via GINERNET
└ 5.134.119.43/321GINERNETGINERNETASSIGNED PADec 20, 2018abuse@ginernet.com
via GINERNET
└ 5.134.119.44/321GINERNETGINERNETASSIGNED PADec 14, 2023abuse@ginernet.com
via GINERNET
└ 5.134.119.45/321GINERNETGINERNETASSIGNED PADec 20, 2018abuse@ginernet.com
via GINERNET
└ 5.134.119.46/321GINERNETGINERNETASSIGNED PAAug 25, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.47/321GINERNETGINERNETASSIGNED PAMar 9, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.48/321GINERNETGINERNETASSIGNED PADec 21, 2018abuse@ginernet.com
via GINERNET
└ 5.134.119.50/321GINERNETGINERNETASSIGNED PADec 22, 2018abuse@ginernet.com
via GINERNET
└ 5.134.119.51/321GINERNETGINERNETASSIGNED PAJan 11, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.52/321GINERNETGINERNETASSIGNED PADec 27, 2018abuse@ginernet.com
via GINERNET
└ 5.134.119.53/321GINERNETGINERNETASSIGNED PAJan 3, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.54/321GINERNETGINERNETASSIGNED PAJan 6, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.55/321GINERNETGINERNETASSIGNED PAMar 23, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.56/321GINERNETGINERNETASSIGNED PAApr 8, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.57/321GINERNETGINERNETASSIGNED PAJun 9, 2024abuse@ginernet.com
via GINERNET
└ 5.134.119.58/321GINERNETGINERNETASSIGNED PASep 24, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.59/321GINERNETGINERNETASSIGNED PAFeb 26, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.60/321GINERNETGINERNETASSIGNED PAJan 7, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.61/321GINERNETGINERNETASSIGNED PAJun 26, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.62/321GINERNETGINERNETASSIGNED PAJul 24, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.63/321GINERNETGINERNETASSIGNED PAJan 7, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.64/321GINERNETGINERNETASSIGNED PAJul 23, 2024abuse@ginernet.com
via GINERNET
└ 5.134.119.65/321GINERNETGINERNETASSIGNED PAOct 7, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.66/321GINERNETGINERNETASSIGNED PAAug 27, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.67/321GINERNETGINERNETASSIGNED PAApr 2, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.68/321GINERNETGINERNETASSIGNED PASep 3, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.69/321GINERNETGINERNETASSIGNED PASep 3, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.70/321GINERNETGINERNETASSIGNED PASep 3, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.71/321GINERNETGINERNETASSIGNED PASep 3, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.72/321GINERNETGINERNETASSIGNED PAMar 29, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.73/321GINERNETGINERNETASSIGNED PAMar 15, 2024abuse@ginernet.com
via GINERNET
└ 5.134.119.74/321GINERNETGINERNETASSIGNED PAMar 16, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.75/321GINERNETGINERNETASSIGNED PAApr 13, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.76/321GINERNETGINERNETASSIGNED PAFeb 19, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.77/321GINERNETGINERNETASSIGNED PAMar 22, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.78/321GINERNETGINERNETASSIGNED PAFeb 9, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.79/321GINERNETGINERNETASSIGNED PAMay 20, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.80/321GINERNETGINERNETASSIGNED PAOct 12, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.81/321GINERNETGINERNETASSIGNED PAJan 8, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.82/321GINERNETGINERNETASSIGNED PAJan 8, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.83/321GINERNETGINERNETASSIGNED PAMar 10, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.84/321GINERNETGINERNETASSIGNED PAJan 24, 2023abuse@ginernet.com
via GINERNET
└ 5.134.119.85/321GINERNETGINERNETASSIGNED PASep 26, 2024abuse@ginernet.com
via GINERNET
└ 5.134.119.86/321GINERNETGINERNETASSIGNED PAJan 8, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.87/321GINERNETGINERNETASSIGNED PAJan 8, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.88/321GINERNETGINERNETASSIGNED PAJan 8, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.89/321GINERNETGINERNETASSIGNED PAMay 27, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.90/321GINERNETGINERNETASSIGNED PAMar 25, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.91/321GINERNETGINERNETASSIGNED PAJul 15, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.92/321GINERNETGINERNETASSIGNED PAOct 11, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.93/321GINERNETGINERNETASSIGNED PAMay 25, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.94/321GINERNETGINERNETASSIGNED PAApr 8, 2025abuse@ginernet.com
via GINERNET
└ 5.134.119.95/321GINERNETGINERNETASSIGNED PAMay 26, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.96/321GINERNETGINERNETASSIGNED PANov 12, 2021abuse@ginernet.com
via GINERNET
└ 5.134.119.97/321GINERNETGINERNETASSIGNED PAOct 11, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.98/321GINERNETGINERNETASSIGNED PADec 18, 2021abuse@ginernet.com
via GINERNET
└ 5.134.119.99/321GINERNETGINERNETASSIGNED PAJan 18, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.100/321GINERNETGINERNETASSIGNED PAJul 10, 2024abuse@ginernet.com
via GINERNET
└ 5.134.119.101/321GINERNETGINERNETASSIGNED PAFeb 6, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.103/321GINERNETGINERNETASSIGNED PAFeb 7, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.104/321GINERNETGINERNETASSIGNED PAFeb 8, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.105/321GINERNETGINERNETASSIGNED PADec 19, 2021abuse@ginernet.com
via GINERNET
└ 5.134.119.106/321GINERNETGINERNETASSIGNED PAMar 24, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.107/321GINERNETGINERNETASSIGNED PAJul 11, 2023abuse@ginernet.com
via GINERNET
└ 5.134.119.108/321GINERNETGINERNETASSIGNED PANov 5, 2023abuse@ginernet.com
via GINERNET
└ 5.134.119.109/321GINERNETGINERNETASSIGNED PAJun 11, 2021abuse@ginernet.com
via GINERNET
└ 5.134.119.110/321GINERNETGINERNETASSIGNED PASep 13, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.111/321GINERNETGINERNETASSIGNED PAAug 9, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.112/321GINERNETGINERNETASSIGNED PADec 8, 2023abuse@ginernet.com
via GINERNET
└ 5.134.119.113/321GINERNETGINERNETASSIGNED PAApr 18, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.114/321GINERNETGINERNETASSIGNED PANov 23, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.115/321GINERNETGINERNETASSIGNED PAJun 6, 2024abuse@ginernet.com
via GINERNET
└ 5.134.119.116/321GINERNETGINERNETASSIGNED PAFeb 8, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.117/321GINERNETGINERNETASSIGNED PADec 17, 2024abuse@ginernet.com
via GINERNET
└ 5.134.119.118/321GINERNETGINERNETASSIGNED PAFeb 10, 2024abuse@ginernet.com
via GINERNET
└ 5.134.119.119/321GINERNETGINERNETASSIGNED PAMar 18, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.120/321GINERNETGINERNETASSIGNED PAJul 16, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.121/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.119.122/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.119.123/321GINERNETGINERNETASSIGNED PAJan 30, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.124/321GINERNETGINERNETASSIGNED PAAug 12, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.125/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.119.126/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.119.127/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.119.128/321GINERNETGINERNETASSIGNED PAOct 25, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.129/321GINERNETGINERNETASSIGNED PASep 21, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.130/321GINERNETGINERNETASSIGNED PAJul 12, 2023abuse@ginernet.com
via GINERNET
└ 5.134.119.131/321GINERNETGINERNETASSIGNED PAApr 4, 2025abuse@ginernet.com
via GINERNET
└ 5.134.119.132/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.119.133/321GINERNETGINERNETASSIGNED PAFeb 15, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.134/321GINERNETGINERNETASSIGNED PAJun 18, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.135/321GINERNETGINERNETASSIGNED PAApr 17, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.136/321GINERNETGINERNETASSIGNED PAJun 28, 2021abuse@ginernet.com
via GINERNET
└ 5.134.119.137/321GINERNETGINERNETASSIGNED PAJun 29, 2021abuse@ginernet.com
via GINERNET
└ 5.134.119.138/321GINERNETGINERNETASSIGNED PADec 22, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.139/321GINERNETGINERNETASSIGNED PAJul 1, 2021abuse@ginernet.com
via GINERNET
└ 5.134.119.140/321GINERNETGINERNETASSIGNED PAJul 4, 2021abuse@ginernet.com
via GINERNET
└ 5.134.119.141/321GINERNETGINERNETASSIGNED PAJul 5, 2021abuse@ginernet.com
via GINERNET
└ 5.134.119.142/321GINERNETGINERNETASSIGNED PAJul 12, 2023abuse@ginernet.com
via GINERNET
└ 5.134.119.143/321GINERNETGINERNETASSIGNED PAJul 6, 2021abuse@ginernet.com
via GINERNET
└ 5.134.119.144/312GINERNETGINERNETASSIGNED PAApr 29, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.146/321GINERNETGINERNETASSIGNED PAJul 24, 2024abuse@ginernet.com
via GINERNET
└ 5.134.119.147/321GINERNETGINERNETASSIGNED PAJun 18, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.148/321GINERNETGINERNETASSIGNED PAApr 9, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.149/321GINERNETGINERNETASSIGNED PAMay 17, 2024abuse@ginernet.com
via GINERNET
└ 5.134.119.150/321GINERNETGINERNETASSIGNED PAMar 23, 2024abuse@ginernet.com
via GINERNET
└ 5.134.119.151/321GINERNETGINERNETASSIGNED PAFeb 26, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.152/304GINERNETGINERNETASSIGNED PAJan 19, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.156/321GINERNETGINERNETASSIGNED PANov 24, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.157/321GINERNETGINERNETASSIGNED PAJun 14, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.158/321GINERNETGINERNETASSIGNED PAJan 19, 2025abuse@ginernet.com
via GINERNET
└ 5.134.119.159/321GINERNETGINERNETASSIGNED PASep 4, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.160/321GINERNETGINERNETASSIGNED PANov 24, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.161/321GINERNETGINERNETASSIGNED PASep 4, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.162/321GINERNETGINERNETASSIGNED PASep 4, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.163/321GINERNETGINERNETASSIGNED PAOct 31, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.164/321GINERNETGINERNETASSIGNED PANov 12, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.165/321GINERNETGINERNETASSIGNED PAMay 3, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.166/321GINERNETGINERNETASSIGNED PAApr 3, 2023abuse@ginernet.com
via GINERNET
└ 5.134.119.167/321GINERNETGINERNETASSIGNED PAJul 10, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.168/321GINERNETGINERNETASSIGNED PAJan 31, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.169/321GINERNETGINERNETASSIGNED PAOct 11, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.170/321GINERNETGINERNETASSIGNED PAJul 10, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.171/321GINERNETGINERNETASSIGNED PAMay 27, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.172/321GINERNETGINERNETASSIGNED PAOct 13, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.173/321GINERNETGINERNETASSIGNED PAJun 18, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.174/321GINERNETGINERNETASSIGNED PAOct 13, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.175/321GINERNETGINERNETASSIGNED PANov 10, 2023abuse@ginernet.com
via GINERNET
└ 5.134.119.176/321GINERNETGINERNETASSIGNED PAMay 8, 2025abuse@ginernet.com
via GINERNET
└ 5.134.119.177/321GINERNETGINERNETASSIGNED PAJul 20, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.178/321GINERNETGINERNETASSIGNED PAOct 10, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.179/321GINERNETGINERNETASSIGNED PANov 24, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.180/304COMYTELCOMYTELASSIGNED PAJul 18, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.184/304GINERNETGINERNETASSIGNED PAMar 12, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.188/321GINERNETGINERNETASSIGNED PAJun 11, 2025abuse@ginernet.com
via GINERNET
└ 5.134.119.189/321GINERNETGINERNETASSIGNED PAOct 10, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.190/321GINERNETGINERNETASSIGNED PAMay 16, 2025abuse@ginernet.com
via GINERNET
└ 5.134.119.191/321GINERNETGINERNETASSIGNED PAAug 24, 2024abuse@ginernet.com
via GINERNET
└ 5.134.119.192/321GINERNETGINERNETASSIGNED PAOct 8, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.193/321GINERNETGINERNETASSIGNED PANov 25, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.194/321GINERNETGINERNETASSIGNED PASep 5, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.195/321GINERNETGINERNETASSIGNED PANov 25, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.196/321GINERNETGINERNETASSIGNED PAOct 19, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.197/321GINERNETGINERNETASSIGNED PAOct 21, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.198/321GINERNETGINERNETASSIGNED PANov 25, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.199/321GINERNETGINERNETASSIGNED PAAug 19, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.200/321GINERNETGINERNETASSIGNED PAJan 11, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.201/321GINERNETGINERNETASSIGNED PAMar 1, 2025abuse@ginernet.com
via GINERNET
└ 5.134.119.202/312GINERNETGINERNETASSIGNED PAMar 30, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.204/321GINERNETGINERNETASSIGNED PAOct 31, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.205/321GINERNETGINERNETASSIGNED PAOct 4, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.206/321GINERNETGINERNETASSIGNED PAJul 15, 2024abuse@ginernet.com
via GINERNET
└ 5.134.119.207/321GINERNETGINERNETASSIGNED PANov 25, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.208/321GINERNETGINERNETASSIGNED PAFeb 28, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.209/321GINERNETGINERNETASSIGNED PANov 25, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.210/321GINERNETGINERNETASSIGNED PAOct 12, 2023abuse@ginernet.com
via GINERNET
└ 5.134.119.211/321GINERNETGINERNETASSIGNED PANov 25, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.212/321GINERNETGINERNETASSIGNED PANov 15, 2021abuse@ginernet.com
via GINERNET
└ 5.134.119.213/321GINERNETGINERNETASSIGNED PANov 15, 2021abuse@ginernet.com
via GINERNET
└ 5.134.119.214/321GINERNETGINERNETASSIGNED PANov 15, 2021abuse@ginernet.com
via GINERNET
└ 5.134.119.215/321GINERNETGINERNETASSIGNED PANov 25, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.216/321GINERNETGINERNETASSIGNED PANov 18, 2021abuse@ginernet.com
via GINERNET
└ 5.134.119.217/321GINERNETGINERNETASSIGNED PAJun 10, 2024abuse@ginernet.com
via GINERNET
└ 5.134.119.218/321GINERNETGINERNETASSIGNED PANov 26, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.219/321GINERNETGINERNETASSIGNED PANov 19, 2021abuse@ginernet.com
via GINERNET
└ 5.134.119.220/321GINERNETGINERNETASSIGNED PAJul 1, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.221/321GINERNETGINERNETASSIGNED PAJul 1, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.222/321GINERNETGINERNETASSIGNED PAJan 16, 2023abuse@ginernet.com
via GINERNET
└ 5.134.119.223/321GINERNETGINERNETASSIGNED PAOct 26, 2024abuse@ginernet.com
via GINERNET
└ 5.134.119.224/321GINERNETGINERNETASSIGNED PANov 7, 2019abuse@ginernet.com
via GINERNET
└ 5.134.119.225/321GINERNETGINERNETASSIGNED PAOct 22, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.226/321GINERNETGINERNETASSIGNED PAApr 14, 2020abuse@ginernet.com
via GINERNET
└ 5.134.119.227/321GINERNETGINERNETASSIGNED PANov 29, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.229/321GINERNETGINERNETASSIGNED PAMar 17, 2023abuse@ginernet.com
via GINERNET
└ 5.134.119.230/321GINERNETGINERNETASSIGNED PAOct 16, 2023abuse@ginernet.com
via GINERNET
└ 5.134.119.231/321GINERNETGINERNETASSIGNED PAApr 4, 2023abuse@ginernet.com
via GINERNET
└ 5.134.119.232/321GINERNETGINERNETASSIGNED PAFeb 22, 2023abuse@ginernet.com
via GINERNET
└ 5.134.119.233/321GINERNETGINERNETASSIGNED PAOct 10, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.234/321GINERNETGINERNETASSIGNED PAOct 10, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.235/321GINERNETGINERNETASSIGNED PAOct 10, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.236/321GINERNETGINERNETASSIGNED PAOct 10, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.237/321GINERNETGINERNETASSIGNED PAJan 18, 2023abuse@ginernet.com
via GINERNET
└ 5.134.119.238/321GINERNETGINERNETASSIGNED PAOct 13, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.239/321GINERNETGINERNETASSIGNED PADec 1, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.240/321GINERNETGINERNETASSIGNED PAJan 18, 2023abuse@ginernet.com
via GINERNET
└ 5.134.119.241/321GINERNETGINERNETASSIGNED PAFeb 22, 2023abuse@ginernet.com
via GINERNET
└ 5.134.119.242/321GINERNETGINERNETASSIGNED PAOct 11, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.243/321GINERNETGINERNETASSIGNED PAOct 11, 2022abuse@ginernet.com
via GINERNET
└ 5.134.119.244/321GINERNETGINERNETASSIGNED PAFeb 22, 2023abuse@ginernet.com
via GINERNET
← Previous1–200 of 204 · 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.119.0/24
Reallocation type
LIR-PARTITIONED PA
Reallocated
Feb 1, 2020
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