Data as of Nov 6, 2026

5.134.115.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.115.0/24256GINERNETGINERNETLIR-PARTITIONED PAOct 27, 2018abuse@ginernet.com
via ES-GINERNET-20120710
└ 5.134.115.0/2816GINERNETGINERNETASSIGNED PAFeb 5, 2020abuse@ginernet.com
via GINERNET
└ 5.134.115.16/304GINERNETGINERNETASSIGNED PAFeb 5, 2020abuse@ginernet.com
via GINERNET
└ 5.134.115.22/312GINERNETGINERNETASSIGNED PAJun 18, 2020abuse@ginernet.com
via GINERNET
└ 5.134.115.25/321GINERNETGINERNETASSIGNED PAFeb 5, 2020abuse@ginernet.com
via GINERNET
└ 5.134.115.26/321GINERNETGINERNETASSIGNED PAFeb 5, 2020abuse@ginernet.com
via GINERNET
└ 5.134.115.28/312GINERNETGINERNETASSIGNED PAJun 18, 2020abuse@ginernet.com
via GINERNET
└ 5.134.115.31/321GINERNETGINERNETASSIGNED PAFeb 5, 2020abuse@ginernet.com
via GINERNET
└ 5.134.115.34/321GINERNETGINERNETASSIGNED PAJan 10, 2021abuse@ginernet.com
via GINERNET
└ 5.134.115.35/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.37/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.40/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.43/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.45/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.48/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.56/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.57/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.62/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.77/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.78/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.79/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.80/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.81/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.84/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.88/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.91/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.99/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.100/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.101/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.103/321GINERNETGINERNETASSIGNED PASep 4, 2019abuse@ginernet.com
via GINERNET
└ 5.134.115.107/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.110/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.111/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.113/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.114/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.116/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.117/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.118/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.119/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.120/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.121/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.123/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.124/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.125/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.127/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.130/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.131/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.132/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.134/321GINERNETGINERNETASSIGNED PAJan 10, 2021abuse@ginernet.com
via GINERNET
└ 5.134.115.135/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.140/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.142/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.145/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.146/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.148/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.150/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.151/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.153/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.154/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.158/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.159/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.160/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.161/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.162/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.163/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.164/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.165/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.166/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.167/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.168/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.169/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.170/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.173/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.175/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.176/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.177/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.178/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.181/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.182/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.183/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.186/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.187/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.188/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.189/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.191/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.193/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.194/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.195/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.196/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.197/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.198/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.200/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.202/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.203/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.204/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.206/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.210/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.211/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.212/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.213/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.214/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.216/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.217/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.218/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.220/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.221/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.222/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.223/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.225/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.227/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.229/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.230/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.231/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.232/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.234/321GINERNETGINERNETASSIGNED PAJan 10, 2021abuse@ginernet.com
via GINERNET
└ 5.134.115.235/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.237/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.238/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.239/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.240/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.241/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.242/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.243/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.244/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.246/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.247/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.115.248/321GINERNETGINERNETASSIGNED PAFeb 5, 2020abuse@ginernet.com
via GINERNET
└ 5.134.115.250/312GINERNETGINERNETASSIGNED PAFeb 5, 2020abuse@ginernet.com
via GINERNET
└ 5.134.115.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.115.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