Data as of Nov 14, 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 15, 2026 – Nov 13, 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.116.114/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.115/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.117/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.118/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.119/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.120/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.122/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.123/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.124/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.126/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.127/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.128/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.130/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.131/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.132/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.133/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 17, 2024abuse@ginernet.com
via 5.134.116.0/24
5.134.116.136/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PAJan 10, 2021abuse@ginernet.com
via 5.134.116.0/24
5.134.116.137/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.139/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.140/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PAJan 30, 2020abuse@ginernet.com
via 5.134.116.0/24
5.134.116.145/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PAJan 30, 2020abuse@ginernet.com
via 5.134.116.0/24
5.134.116.147/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PAJan 30, 2020abuse@ginernet.com
via 5.134.116.0/24
5.134.116.150/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PAJan 30, 2020abuse@ginernet.com
via 5.134.116.0/24
5.134.116.151/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PAJan 30, 2020abuse@ginernet.com
via 5.134.116.0/24
5.134.116.153/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PAJan 30, 2020abuse@ginernet.com
via 5.134.116.0/24
5.134.116.154/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PAJan 30, 2020abuse@ginernet.com
via 5.134.116.0/24
5.134.116.156/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PAJan 30, 2020abuse@ginernet.com
via 5.134.116.0/24
5.134.116.159/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PAJan 30, 2020abuse@ginernet.com
via 5.134.116.0/24
5.134.116.160/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PAJan 30, 2020abuse@ginernet.com
via 5.134.116.0/24
5.134.116.163/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PAJan 30, 2020abuse@ginernet.com
via 5.134.116.0/24
5.134.116.169/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.171/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.173/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.179/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.180/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.182/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.184/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.187/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.188/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.189/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.190/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.191/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.194/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.196/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.197/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.198/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.199/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.200/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PAOct 29, 2023abuse@ginernet.com
via 5.134.116.0/24
5.134.116.201/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.202/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PAOct 29, 2023abuse@ginernet.com
via 5.134.116.0/24
5.134.116.203/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.204/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PAFeb 26, 2025abuse@ginernet.com
via 5.134.116.0/24
5.134.116.205/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PAFeb 26, 2025abuse@ginernet.com
via 5.134.116.0/24
5.134.116.206/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.207/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.208/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.209/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.211/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.212/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.213/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.215/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PAMar 28, 2025abuse@ginernet.com
via 5.134.116.0/24
5.134.116.216/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.217/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.220/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.221/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.224/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.227/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.228/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.235/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.236/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PAJan 10, 2021abuse@ginernet.com
via 5.134.116.0/24
5.134.116.239/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via 5.134.116.0/24
5.134.116.244/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PADec 17, 2024abuse@ginernet.com
via 5.134.116.0/24
5.134.116.245/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PAFeb 17, 2023abuse@ginernet.com
via 5.134.116.0/24
5.134.116.246/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PADec 12, 2024abuse@ginernet.com
via 5.134.116.0/24
5.134.116.248/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PAJul 5, 2022abuse@ginernet.com
via 5.134.116.0/24
5.134.116.249/32
under 5.134.116.0/24
1GINERNETGINERNETASSIGNED PASep 30, 2022abuse@ginernet.com
via 5.134.116.0/24
5.134.116.250/31
under 5.134.116.0/24
2GINERNETGINERNETASSIGNED PAFeb 5, 2020abuse@ginernet.com
via 5.134.116.0/24
5.134.116.252/30
under 5.134.116.0/24
4GINERNETGINERNETASSIGNED PAFeb 5, 2020abuse@ginernet.com
via 5.134.116.0/24
└ 5.134.117.0/24256GINERNETGINERNETLIR-PARTITIONED PAOct 27, 2018abuse@ginernet.com
via ES-GINERNET-20120710
└ 5.134.117.0/2732GINERNETGINERNETASSIGNED PAApr 25, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.32/321GINERNETGINERNETASSIGNED PAJul 11, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.33/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.34/321GINERNETGINERNETASSIGNED PAMay 13, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.35/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.36/321GINERNETGINERNETASSIGNED PAMay 23, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.37/321GINERNETGINERNETASSIGNED PAJan 10, 2021abuse@ginernet.com
via GINERNET
└ 5.134.117.38/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.39/321GINERNETGINERNETASSIGNED PANov 4, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.40/321GINERNETGINERNETASSIGNED PANov 4, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.41/321GINERNETGINERNETASSIGNED PAMay 24, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.42/321GINERNETGINERNETASSIGNED PAAug 23, 2023abuse@ginernet.com
via GINERNET
└ 5.134.117.43/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.44/321GINERNETGINERNETASSIGNED PASep 6, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.45/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.46/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.47/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.48/321GINERNETGINERNETASSIGNED PANov 28, 2022abuse@ginernet.com
via GINERNET
└ 5.134.117.49/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.51/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.53/321GINERNETGINERNETASSIGNED PAOct 21, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.54/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.55/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.56/321GINERNETGINERNETASSIGNED PAOct 22, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.57/321GINERNETGINERNETASSIGNED PANov 4, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.58/321GINERNETGINERNETASSIGNED PAOct 23, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.59/321GINERNETGINERNETASSIGNED PAOct 23, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.60/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.61/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.62/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.63/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.64/321GINERNETGINERNETASSIGNED PAOct 23, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.65/321GINERNETGINERNETASSIGNED PAOct 23, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.66/321GINERNETGINERNETASSIGNED PAOct 23, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.67/321GINERNETGINERNETASSIGNED PAOct 23, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.68/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.69/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.70/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.71/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.72/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.74/321GINERNETGINERNETASSIGNED PAOct 24, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.75/321GINERNETGINERNETASSIGNED PADec 8, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.76/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.77/321GINERNETGINERNETASSIGNED PANov 8, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.78/321GINERNETGINERNETASSIGNED PAMay 1, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.79/321GINERNETGINERNETASSIGNED PAOct 25, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.80/321GINERNETGINERNETASSIGNED PAOct 14, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.81/321GINERNETGINERNETASSIGNED PAOct 14, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.82/321GINERNETGINERNETASSIGNED PAOct 14, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.83/321GINERNETGINERNETASSIGNED PAOct 14, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.84/321GINERNETGINERNETASSIGNED PADec 8, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.85/321GINERNETGINERNETASSIGNED PANov 8, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.86/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.87/321GINERNETGINERNETASSIGNED PADec 12, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.88/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.89/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.90/321GINERNETGINERNETASSIGNED PAOct 13, 2022abuse@ginernet.com
via GINERNET
└ 5.134.117.91/321GINERNETGINERNETASSIGNED PAOct 13, 2022abuse@ginernet.com
via GINERNET
└ 5.134.117.92/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.93/321GINERNETGINERNETASSIGNED PANov 9, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.94/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.95/321GINERNETGINERNETASSIGNED PANov 9, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.96/321GINERNETGINERNETASSIGNED PANov 25, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.97/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.98/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.99/321GINERNETGINERNETASSIGNED PANov 18, 2023abuse@ginernet.com
via GINERNET
└ 5.134.117.100/321GINERNETGINERNETASSIGNED PAJul 24, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.101/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.102/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.103/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.104/321GINERNETGINERNETASSIGNED PADec 19, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.105/321GINERNETGINERNETASSIGNED PADec 19, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.106/321GINERNETGINERNETASSIGNED PADec 20, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.108/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.109/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.110/321GINERNETGINERNETASSIGNED PADec 20, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.111/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.112/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.113/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.114/321GINERNETGINERNETASSIGNED PADec 21, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.116/321GINERNETGINERNETASSIGNED PADec 21, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.117/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.118/321GINERNETGINERNETASSIGNED PADec 23, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.119/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.120/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.121/321GINERNETGINERNETASSIGNED PADec 26, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.122/321GINERNETGINERNETASSIGNED PADec 26, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.123/321GINERNETGINERNETASSIGNED PADec 26, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.124/321GINERNETGINERNETASSIGNED PADec 26, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.125/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.126/321GINERNETGINERNETASSIGNED PADec 26, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.127/321GINERNETGINERNETASSIGNED PADec 26, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.132/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.137/321GINERNETGINERNETASSIGNED PAJan 10, 2021abuse@ginernet.com
via GINERNET
└ 5.134.117.139/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.141/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.142/321GINERNETGINERNETASSIGNED PAApr 10, 2025abuse@ginernet.com
via GINERNET
└ 5.134.117.143/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.144/321GINERNETGINERNETASSIGNED PAAug 9, 2025abuse@ginernet.com
via GINERNET
└ 5.134.117.149/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.150/321GINERNETGINERNETASSIGNED PAJan 27, 2025abuse@ginernet.com
via GINERNET
└ 5.134.117.151/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.152/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.157/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.160/321GINERNETGINERNETASSIGNED PADec 21, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.161/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.162/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.163/321GINERNETGINERNETASSIGNED PADec 21, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.164/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.165/321GINERNETGINERNETASSIGNED PADec 21, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.166/321GINERNETGINERNETASSIGNED PADec 21, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.167/321GINERNETGINERNETASSIGNED PADec 21, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.168/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.169/321GINERNETGINERNETASSIGNED PADec 21, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.170/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.171/321GINERNETGINERNETASSIGNED PADec 21, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.172/321GINERNETGINERNETASSIGNED PADec 21, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.173/321GINERNETGINERNETASSIGNED PADec 21, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.174/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 5.134.117.175/321GINERNETGINERNETASSIGNED PADec 21, 2024abuse@ginernet.com
via GINERNET
└ 5.134.117.176/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
← Previous201–400 of 865 · page 2 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