Data as of Nov 7, 2026

188.213.4.0/22

No anonymizer space · no proxy exits in 30 days

Ginernet S.L.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting

Announcements

More specific

Announcements inside

PrefixOriginTypeHolderRPKI
188.213.4.0/24
since Nov 2016
AS59432HostingGinernet S.L.
via GINERNET
188.213.5.0/24
since Nov 2016
AS59432HostingGinernet S.L.
via GINERNET
188.213.6.0/24
since Nov 2016
AS59432HostingGinernet S.L.
via GINERNET
188.213.7.0/24
since Nov 2016
AS59432HostingGinernet S.L.
via GINERNET AntiDDoS - Path.net DDoS Protected IPs

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
188.213.4.0/221,024ES-GINERNET-20090508Ginernet S.L. (ORG-JMG1-RIPE) · ESALLOCATED PAOct 1, 2013abuse@ginernet.com
└ 188.213.4.0/24256GINERNETGINERNETLIR-PARTITIONED PANov 30, 2018abuse@ginernet.com
via ES-GINERNET-20090508
└ 188.213.4.0/25128GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 188.213.4.128/25128GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 188.213.5.0/24256GINERNETGINERNETLIR-PARTITIONED PAOct 27, 2018abuse@ginernet.com
via ES-GINERNET-20090508
└ 188.213.5.0/2816GINERNETGINERNETASSIGNED PAFeb 5, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.16/298GINERNETGINERNETASSIGNED PAAug 31, 2021abuse@ginernet.com
via GINERNET
└ 188.213.5.24/304GINERNETGINERNETASSIGNED PAFeb 5, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.28/312GINERNETGINERNETASSIGNED PAFeb 5, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.30/321GINERNETGINERNETASSIGNED PAAug 31, 2021abuse@ginernet.com
via GINERNET
└ 188.213.5.32/321GINERNETGINERNETASSIGNED PAAug 3, 2021abuse@ginernet.com
via GINERNET
└ 188.213.5.33/321GINERNETGINERNETASSIGNED PAMar 14, 2025abuse@ginernet.com
via GINERNET
└ 188.213.5.34/321GINERNETGINERNETASSIGNED PADec 1, 2022abuse@ginernet.com
via GINERNET
└ 188.213.5.35/321GINERNETGINERNETASSIGNED PAJan 10, 2021abuse@ginernet.com
via GINERNET
└ 188.213.5.36/321GINERNETGINERNETASSIGNED PADec 1, 2022abuse@ginernet.com
via GINERNET
└ 188.213.5.37/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.38/321GINERNETGINERNETASSIGNED PAFeb 25, 2022abuse@ginernet.com
via GINERNET
└ 188.213.5.39/321GINERNETGINERNETASSIGNED PAFeb 10, 2024abuse@ginernet.com
via GINERNET
└ 188.213.5.40/321GINERNETGINERNETASSIGNED PAMay 22, 2025abuse@ginernet.com
via GINERNET
└ 188.213.5.41/321GINERNETGINERNETASSIGNED PANov 11, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.42/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.43/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.44/321GINERNETGINERNETASSIGNED PAFeb 1, 2025abuse@ginernet.com
via GINERNET
└ 188.213.5.45/321GINERNETGINERNETASSIGNED PAAug 6, 2024abuse@ginernet.com
via GINERNET
└ 188.213.5.46/321GINERNETGINERNETASSIGNED PAFeb 24, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.47/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.48/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.49/321GINERNETGINERNETASSIGNED PADec 1, 2022abuse@ginernet.com
via GINERNET
└ 188.213.5.50/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.51/321GINERNETGINERNETASSIGNED PAFeb 24, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.52/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.53/321GINERNETGINERNETASSIGNED PADec 1, 2022abuse@ginernet.com
via GINERNET
└ 188.213.5.54/321GINERNETGINERNETASSIGNED PAAug 22, 2021abuse@ginernet.com
via GINERNET
└ 188.213.5.55/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.56/321GINERNETGINERNETASSIGNED PAMar 13, 2025abuse@ginernet.com
via GINERNET
└ 188.213.5.57/321GINERNETGINERNETASSIGNED PADec 1, 2022abuse@ginernet.com
via GINERNET
└ 188.213.5.58/321GINERNETGINERNETASSIGNED PAJun 10, 2022abuse@ginernet.com
via GINERNET
└ 188.213.5.59/321GINERNETGINERNETASSIGNED PAJun 11, 2022abuse@ginernet.com
via GINERNET
└ 188.213.5.60/321GINERNETGINERNETASSIGNED PAMay 16, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.61/321GINERNETGINERNETASSIGNED PADec 1, 2022abuse@ginernet.com
via GINERNET
└ 188.213.5.62/321GINERNETGINERNETASSIGNED PAJun 5, 2025abuse@ginernet.com
via GINERNET
└ 188.213.5.63/321GINERNETGINERNETASSIGNED PAFeb 10, 2022abuse@ginernet.com
via GINERNET
└ 188.213.5.64/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.65/321GINERNETGINERNETASSIGNED PADec 2, 2022abuse@ginernet.com
via GINERNET
└ 188.213.5.66/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.67/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.68/321GINERNETGINERNETASSIGNED PAFeb 24, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.69/321GINERNETGINERNETASSIGNED PAFeb 10, 2022abuse@ginernet.com
via GINERNET
└ 188.213.5.70/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.71/321GINERNETGINERNETASSIGNED PADec 2, 2022abuse@ginernet.com
via GINERNET
└ 188.213.5.72/321GINERNETGINERNETASSIGNED PAMay 13, 2025abuse@ginernet.com
via GINERNET
└ 188.213.5.73/321GINERNETGINERNETASSIGNED PAFeb 24, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.74/321GINERNETGINERNETASSIGNED PAJan 24, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.75/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.76/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.77/321GINERNETGINERNETASSIGNED PASep 2, 2021abuse@ginernet.com
via GINERNET
└ 188.213.5.78/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.79/321GINERNETGINERNETASSIGNED PAOct 15, 2021abuse@ginernet.com
via GINERNET
└ 188.213.5.80/321GINERNETGINERNETASSIGNED PAAug 2, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.81/321GINERNETGINERNETASSIGNED PAMar 14, 2025abuse@ginernet.com
via GINERNET
└ 188.213.5.82/321GINERNETGINERNETASSIGNED PAJan 17, 2024abuse@ginernet.com
via GINERNET
└ 188.213.5.83/321GINERNETGINERNETASSIGNED PAJul 25, 2022abuse@ginernet.com
via GINERNET
└ 188.213.5.84/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.85/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.86/321GINERNETGINERNETASSIGNED PANov 6, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.87/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.88/321GINERNETGINERNETASSIGNED PADec 2, 2022abuse@ginernet.com
via GINERNET
└ 188.213.5.89/321GINERNETGINERNETASSIGNED PANov 18, 2024abuse@ginernet.com
via GINERNET
└ 188.213.5.90/321GINERNETGINERNETASSIGNED PASep 6, 2021abuse@ginernet.com
via GINERNET
└ 188.213.5.91/321GINERNETGINERNETASSIGNED PAMar 15, 2025abuse@ginernet.com
via GINERNET
└ 188.213.5.92/321GINERNETGINERNETASSIGNED PAMar 3, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.93/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.94/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.95/321GINERNETGINERNETASSIGNED PAFeb 10, 2022abuse@ginernet.com
via GINERNET
└ 188.213.5.96/321GINERNETGINERNETASSIGNED PAMar 3, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.97/321GINERNETGINERNETASSIGNED PASep 16, 2021abuse@ginernet.com
via GINERNET
└ 188.213.5.98/321GINERNETGINERNETASSIGNED PAMar 3, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.99/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.100/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.101/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.102/321GINERNETGINERNETASSIGNED PAJan 5, 2025abuse@ginernet.com
via GINERNET
└ 188.213.5.103/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.104/321GINERNETGINERNETASSIGNED PAMay 15, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.105/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.106/321GINERNETGINERNETASSIGNED PAAug 6, 2025abuse@ginernet.com
via GINERNET
└ 188.213.5.107/321GINERNETGINERNETASSIGNED PAMar 5, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.108/321GINERNETGINERNETASSIGNED PAFeb 5, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.109/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.110/321GINERNETGINERNETASSIGNED PADec 5, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.111/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.112/321GINERNETGINERNETASSIGNED PAMar 6, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.113/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.114/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.115/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.116/321GINERNETGINERNETASSIGNED PADec 7, 2022abuse@ginernet.com
via GINERNET
└ 188.213.5.117/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.118/321GINERNETGINERNETASSIGNED PAFeb 3, 2025abuse@ginernet.com
via GINERNET
└ 188.213.5.119/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.120/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.121/321GINERNETGINERNETASSIGNED PADec 15, 2021abuse@ginernet.com
via GINERNET
└ 188.213.5.122/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.123/321GINERNETGINERNETASSIGNED PAAug 3, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.124/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.125/321GINERNETGINERNETASSIGNED PAMar 7, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.126/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.127/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.128/321GINERNETGINERNETASSIGNED PAMar 7, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.129/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.130/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.131/321GINERNETGINERNETASSIGNED PANov 7, 2024abuse@ginernet.com
via GINERNET
└ 188.213.5.132/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.133/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.135/321GINERNETGINERNETASSIGNED PANov 30, 2018abuse@ginernet.com
via GINERNET
└ 188.213.5.136/321GINERNETGINERNETASSIGNED PANov 27, 2021abuse@ginernet.com
via GINERNET
└ 188.213.5.137/321GINERNETGINERNETASSIGNED PANov 28, 2021abuse@ginernet.com
via GINERNET
└ 188.213.5.138/321GINERNETGINERNETASSIGNED PAFeb 7, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.139/321GINERNETGINERNETASSIGNED PANov 29, 2021abuse@ginernet.com
via GINERNET
└ 188.213.5.140/321GINERNETGINERNETASSIGNED PAAug 21, 2024abuse@ginernet.com
via GINERNET
└ 188.213.5.141/321GINERNETGINERNETASSIGNED PAJul 29, 2025abuse@ginernet.com
via GINERNET
└ 188.213.5.142/321GINERNETGINERNETASSIGNED PAOct 3, 2024abuse@ginernet.com
via GINERNET
└ 188.213.5.143/321GINERNETGINERNETASSIGNED PAMar 7, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.144/321GINERNETGINERNETASSIGNED PAMar 7, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.145/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.146/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.147/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.148/321GINERNETGINERNETASSIGNED PASep 5, 2024abuse@ginernet.com
via GINERNET
└ 188.213.5.149/321GINERNETGINERNETASSIGNED PAApr 15, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.150/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.151/321GINERNETGINERNETASSIGNED PAMar 19, 2022abuse@ginernet.com
via GINERNET
└ 188.213.5.152/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.153/321GINERNETGINERNETASSIGNED PAOct 18, 2021abuse@ginernet.com
via GINERNET
└ 188.213.5.154/321GINERNETGINERNETASSIGNED PAApr 17, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.155/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.156/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.157/321GINERNETGINERNETASSIGNED PAMay 9, 2025abuse@ginernet.com
via GINERNET
└ 188.213.5.158/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.159/321GINERNETGINERNETASSIGNED PAApr 17, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.160/321GINERNETGINERNETASSIGNED PAJan 29, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.161/321GINERNETGINERNETASSIGNED PANov 30, 2024abuse@ginernet.com
via GINERNET
└ 188.213.5.162/321GINERNETGINERNETASSIGNED PAMay 17, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.163/321GINERNETGINERNETASSIGNED PAMay 6, 2022abuse@ginernet.com
via GINERNET
└ 188.213.5.164/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.166/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.167/321GINERNETGINERNETASSIGNED PAOct 26, 2021abuse@ginernet.com
via GINERNET
└ 188.213.5.168/321GINERNETGINERNETASSIGNED PAApr 20, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.169/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.170/321GINERNETGINERNETASSIGNED PAMay 20, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.171/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.172/321GINERNETGINERNETASSIGNED PADec 6, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.173/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.174/321GINERNETGINERNETASSIGNED PADec 2, 2021abuse@ginernet.com
via GINERNET
└ 188.213.5.175/321GINERNETGINERNETASSIGNED PAOct 4, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.176/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.177/321GINERNETGINERNETASSIGNED PAApr 21, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.178/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.179/321GINERNETGINERNETASSIGNED PAOct 26, 2021abuse@ginernet.com
via GINERNET
└ 188.213.5.180/312GINERNETGINERNETASSIGNED PAOct 26, 2021abuse@ginernet.com
via GINERNET
└ 188.213.5.182/321GINERNETGINERNETASSIGNED PAOct 26, 2021abuse@ginernet.com
via GINERNET
└ 188.213.5.183/321GINERNETGINERNETASSIGNED PANov 20, 2024abuse@ginernet.com
via GINERNET
└ 188.213.5.184/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.185/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.186/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.187/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.188/321GINERNETGINERNETASSIGNED PAMay 21, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.189/321GINERNETGINERNETASSIGNED PAMay 21, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.190/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.191/321GINERNETGINERNETASSIGNED PAMay 23, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.192/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.193/321GINERNETGINERNETASSIGNED PAMay 24, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.194/321GINERNETGINERNETASSIGNED PAMay 24, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.195/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.196/321GINERNETGINERNETASSIGNED PADec 1, 2022abuse@ginernet.com
via GINERNET
└ 188.213.5.197/321GINERNETGINERNETASSIGNED PAMay 25, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.198/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.199/321GINERNETGINERNETASSIGNED PAMay 25, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.200/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.201/321GINERNETGINERNETASSIGNED PAOct 11, 2024abuse@ginernet.com
via GINERNET
└ 188.213.5.202/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.203/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.204/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.205/321GINERNETGINERNETASSIGNED PAMay 23, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.206/321GINERNETGINERNETASSIGNED PAJun 12, 2025abuse@ginernet.com
via GINERNET
└ 188.213.5.207/321GINERNETGINERNETASSIGNED PAJun 7, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.208/321GINERNETGINERNETASSIGNED PAJun 8, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.209/321GINERNETGINERNETASSIGNED PAJun 15, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.210/321GINERNETGINERNETASSIGNED PAJun 15, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.211/321GINERNETGINERNETASSIGNED PAJun 15, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.212/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.213/321GINERNETGINERNETASSIGNED PAMar 16, 2021abuse@ginernet.com
via GINERNET
└ 188.213.5.214/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.215/321GINERNETGINERNETASSIGNED PAJul 5, 2022abuse@ginernet.com
via GINERNET
└ 188.213.5.216/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.217/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.218/321GINERNETGINERNETASSIGNED PAJun 17, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.219/321GINERNETGINERNETASSIGNED PAFeb 28, 2024abuse@ginernet.com
via GINERNET
└ 188.213.5.220/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.221/321GINERNETGINERNETASSIGNED PAMay 7, 2022abuse@ginernet.com
via GINERNET
└ 188.213.5.222/321GINERNETGINERNETASSIGNED PAJun 19, 2023abuse@ginernet.com
via GINERNET
└ 188.213.5.223/321GINERNETGINERNETASSIGNED PAJun 20, 2024abuse@ginernet.com
via GINERNET
└ 188.213.5.224/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
└ 188.213.5.225/321GINERNETGINERNETASSIGNED PAFeb 4, 2020abuse@ginernet.com
via GINERNET
← Previous1–200 of 412 · page 1 of 3Next →

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