Data as of Nov 6, 2026

5.134.112.0/21

1 residential-proxy exit · 30 days

Ginernet S.L.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting

Residential-proxy exits

Proxy exits
1
0.05% of its addresses · 30 days
Spread
1 of 8
/24s with at least one exit
Providers
3
selling exits here
Oct 7, 2026 – Nov 5, 2026

Exits seen per day

3 observations

Proxy providers listing exits

  • GloryCloud
  • KindProxy
  • PuraRoute

Announcements

Nesting

More-specifics by size

Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
5.134.112.0/24
since Mar 2015
AS59432HostingGinernet S.L.
via GINERNET
5.134.113.0/24
since Jul 2014
AS59432HostingGinernet S.L.
via GINERNET
5.134.114.0/24
since Oct 2025
AS59432HostingGinernet S.L.
via GINERNET
5.134.115.0/24
since Aug 2014
AS59432HostingGinernet S.L.
via GINERNET
5.134.116.0/24
since Feb 2015
AS59432HostingGinernet S.L.
via GINERNET
5.134.117.0/24
since Feb 2015
AS59432HostingGinernet S.L.
via GINERNET
5.134.118.0/24
since Jul 2014
AS59432Hosting1Ginernet S.L.
via GINERNET
5.134.119.0/24
since Jul 2014
AS59432HostingGinernet 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
5.134.112.0/212,048ES-GINERNET-20120710Ginernet S.L. (ORG-JMG1-RIPE) · ESALLOCATED PAJul 10, 2012abuse@ginernet.com
└ 5.134.112.0/24256GINERNETGINERNETLIR-PARTITIONED PANov 30, 2018abuse@ginernet.com
via ES-GINERNET-20120710
└ 5.134.113.0/24256GINERNETGINERNETLIR-PARTITIONED PAOct 19, 2018abuse@ginernet.com
via ES-GINERNET-20120710
└ 5.134.113.0/25128GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.113.128/25128GINERNETGINERNETASSIGNED PAApr 25, 2024abuse@ginernet.com
via GINERNET
└ 5.134.114.0/24256GINERNETGINERNETLIR-PARTITIONED PAOct 20, 2018abuse@ginernet.com
via ES-GINERNET-20120710
└ 5.134.114.0/25128GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.114.128/25128GINERNETGINERNETASSIGNED PAFeb 5, 2020abuse@ginernet.com
via GINERNET
└ 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
└ 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
← Previous1–200 of 865 · page 1 of 5Next →

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