Data as of Nov 8, 2026

5.134.116.0/24

No anonymizer space · no proxy exits in 30 days

Ginernet S.L.

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

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.116.0/24256GINERNETGINERNETLIR-PARTITIONED PAOct 27, 2018abuse@ginernet.com
via ES-GINERNET-20120710
└ 5.134.116.0/2816GINERNETGINERNETASSIGNED PASep 30, 2022abuse@ginernet.com
via GINERNET
└ 5.134.116.16/321GINERNETGINERNETASSIGNED PASep 30, 2022abuse@ginernet.com
via GINERNET
└ 5.134.116.17/321GINERNETGINERNETASSIGNED PASep 30, 2022abuse@ginernet.com
via GINERNET
└ 5.134.116.18/312GINERNETGINERNETASSIGNED PASep 30, 2022abuse@ginernet.com
via GINERNET
└ 5.134.116.20/304GINERNETGINERNETASSIGNED PASep 30, 2022abuse@ginernet.com
via GINERNET
└ 5.134.116.32/321GINERNETGINERNETASSIGNED PASep 4, 2023abuse@ginernet.com
via GINERNET
└ 5.134.116.33/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.34/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.35/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.36/321GINERNETGINERNETASSIGNED PAJan 10, 2021abuse@ginernet.com
via GINERNET
└ 5.134.116.40/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.42/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.44/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.45/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.46/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.47/321GINERNETGINERNETASSIGNED PANov 17, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.48/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.49/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.50/321GINERNETGINERNETASSIGNED PANov 19, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.51/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.53/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.56/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.58/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.60/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.63/321GINERNETGINERNETASSIGNED PASep 26, 2022abuse@ginernet.com
via GINERNET
└ 5.134.116.64/321GINERNETGINERNETASSIGNED PADec 27, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.65/321GINERNETGINERNETASSIGNED PADec 27, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.66/321GINERNETGINERNETASSIGNED PADec 27, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.67/321GINERNETGINERNETASSIGNED PADec 27, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.68/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.69/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.70/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.71/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.72/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.73/321GINERNETGINERNETASSIGNED PADec 27, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.74/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.75/321GINERNETGINERNETASSIGNED PADec 27, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.76/321GINERNETGINERNETASSIGNED PADec 27, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.77/321GINERNETGINERNETASSIGNED PADec 27, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.78/321GINERNETGINERNETASSIGNED PADec 27, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.79/321GINERNETGINERNETASSIGNED PADec 27, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.80/321GINERNETGINERNETASSIGNED PADec 27, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.81/321GINERNETGINERNETASSIGNED PADec 27, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.82/321GINERNETGINERNETASSIGNED PADec 27, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.83/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.84/321GINERNETGINERNETASSIGNED PADec 27, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.85/321GINERNETGINERNETASSIGNED PADec 27, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.86/321GINERNETGINERNETASSIGNED PADec 27, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.87/321GINERNETGINERNETASSIGNED PADec 27, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.88/321GINERNETGINERNETASSIGNED PADec 27, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.89/321GINERNETGINERNETASSIGNED PADec 27, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.90/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.91/321GINERNETGINERNETASSIGNED PADec 27, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.92/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.93/321GINERNETGINERNETASSIGNED PADec 27, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.94/321GINERNETGINERNETASSIGNED PADec 27, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.95/321GINERNETGINERNETASSIGNED PADec 27, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.99/321GINERNETGINERNETASSIGNED PAJul 30, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.103/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.104/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.106/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.112/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.113/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.114/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.115/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.117/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.118/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.119/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.120/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.122/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.123/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.124/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.126/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.127/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.128/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.130/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.131/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.132/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.133/321GINERNETGINERNETASSIGNED PANov 17, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.136/321GINERNETGINERNETASSIGNED PAJan 10, 2021abuse@ginernet.com
via GINERNET
└ 5.134.116.137/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.139/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.140/321GINERNETGINERNETASSIGNED PAJan 30, 2020abuse@ginernet.com
via GINERNET
└ 5.134.116.145/321GINERNETGINERNETASSIGNED PAJan 30, 2020abuse@ginernet.com
via GINERNET
└ 5.134.116.147/321GINERNETGINERNETASSIGNED PAJan 30, 2020abuse@ginernet.com
via GINERNET
└ 5.134.116.150/321GINERNETGINERNETASSIGNED PAJan 30, 2020abuse@ginernet.com
via GINERNET
└ 5.134.116.151/321GINERNETGINERNETASSIGNED PAJan 30, 2020abuse@ginernet.com
via GINERNET
└ 5.134.116.153/321GINERNETGINERNETASSIGNED PAJan 30, 2020abuse@ginernet.com
via GINERNET
└ 5.134.116.154/321GINERNETGINERNETASSIGNED PAJan 30, 2020abuse@ginernet.com
via GINERNET
└ 5.134.116.156/321GINERNETGINERNETASSIGNED PAJan 30, 2020abuse@ginernet.com
via GINERNET
└ 5.134.116.159/321GINERNETGINERNETASSIGNED PAJan 30, 2020abuse@ginernet.com
via GINERNET
└ 5.134.116.160/321GINERNETGINERNETASSIGNED PAJan 30, 2020abuse@ginernet.com
via GINERNET
└ 5.134.116.163/321GINERNETGINERNETASSIGNED PAJan 30, 2020abuse@ginernet.com
via GINERNET
└ 5.134.116.169/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.171/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.173/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.179/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.180/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.182/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.184/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.187/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.188/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.189/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.190/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.191/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.194/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.196/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.197/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.198/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.199/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.200/321GINERNETGINERNETASSIGNED PAOct 29, 2023abuse@ginernet.com
via GINERNET
└ 5.134.116.201/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.202/321GINERNETGINERNETASSIGNED PAOct 29, 2023abuse@ginernet.com
via GINERNET
└ 5.134.116.203/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.204/321GINERNETGINERNETASSIGNED PAFeb 26, 2025abuse@ginernet.com
via GINERNET
└ 5.134.116.205/321GINERNETGINERNETASSIGNED PAFeb 26, 2025abuse@ginernet.com
via GINERNET
└ 5.134.116.206/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.207/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.208/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.209/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.211/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.212/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.213/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.215/321GINERNETGINERNETASSIGNED PAMar 28, 2025abuse@ginernet.com
via GINERNET
└ 5.134.116.216/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.217/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.220/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.221/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.224/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.227/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.228/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.235/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.236/321GINERNETGINERNETASSIGNED PAJan 10, 2021abuse@ginernet.com
via GINERNET
└ 5.134.116.239/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.116.244/321GINERNETGINERNETASSIGNED PADec 17, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.245/321GINERNETGINERNETASSIGNED PAFeb 17, 2023abuse@ginernet.com
via GINERNET
└ 5.134.116.246/321GINERNETGINERNETASSIGNED PADec 12, 2024abuse@ginernet.com
via GINERNET
└ 5.134.116.248/321GINERNETGINERNETASSIGNED PAJul 5, 2022abuse@ginernet.com
via GINERNET
└ 5.134.116.249/321GINERNETGINERNETASSIGNED PASep 30, 2022abuse@ginernet.com
via GINERNET
└ 5.134.116.250/312GINERNETGINERNETASSIGNED PAFeb 5, 2020abuse@ginernet.com
via GINERNET
└ 5.134.116.252/304GINERNETGINERNETASSIGNED PAFeb 5, 2020abuse@ginernet.com
via GINERNET

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.116.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