WHOIS Tool for 2.82.222.57
- Tools
- WHOIS Tool for 2.82.222.57
WHOIS Registry Details for IP 2.82.222.57
Information obtained from public network records.
Red
| NetRange | 2.0.0.0 - 2.255.255.255 |
| CIDR | 2.0.0.0/8 |
| NetName | 2-RIPE |
| NetType | Allocated to RIPE NCC |
Organización
| Organization | RIPE Network Coordination Centre (RIPE) |
| OrgName | RIPE Network Coordination Centre |
| Country | NL |
| Address | P.O. Box 10096 |
Contacto directo
| OrgAbuseEmail | abuse@ripe.net |
| OrgAbusePhone | +31205354444 |
| OrgTechEmail | hostmaster@ripe.net |
| OrgTechPhone | +31 20 535 4444 |
Registro
| Updated | 2025-02-10 2013-07-29 |
| RegDate | 2009-09-29 |
Información adicional
| OriginAS | |
| City | Amsterdam |
| StateProv | |
| PostalCode | 1001EB |
| ReferralServer | whois.ripe.net |
| OrgAbuseHandle | ABUSE3850-ARIN |
| OrgAbuseName | Abuse Contact |
| OrgTechHandle | RNO29-ARIN |
| OrgTechName | RIPE NCC Operations |
History of 2.82.222.57
Range 2.80.0.0/14
- 29/04/2010 — present: organization not on record · PT
Route announcements (BGP)
- 11/08/2026 — 01/09/2026: 2.80.0.0/14 announced by AS3243
- 18/07/2026 — 10/08/2026: 2.80.0.0/14 announced by AS3243
- 24/06/2026 — 17/07/2026: 2.80.0.0/14 announced by AS3243
- 07/05/2026 — 23/06/2026: 2.80.0.0/14 announced by AS3243
- 13/04/2026 — 06/05/2026: 2.80.0.0/14 announced by AS3243
- 01/04/2026 — 12/04/2026: 2.80.0.0/14 announced by AS3243
- 08/03/2026 — 31/03/2026: 2.80.0.0/14 announced by AS3243
- 12/02/2026 — 07/03/2026: 2.80.0.0/14 announced by AS3243
- 19/01/2026 — 11/02/2026: 2.80.0.0/14 announced by AS3243
- 26/12/2025 — 18/01/2026: 2.80.0.0/14 announced by AS3243
- 02/12/2025 — 25/12/2025: 2.80.0.0/14 announced by AS3243
- 20/11/2025 — 01/12/2025: 2.80.0.0/14 announced by AS3243
- 27/10/2025 — 19/11/2025: 2.80.0.0/14 announced by AS3243
- 09/09/2025 — 26/10/2025: 2.80.0.0/14 announced by AS3243
- 16/08/2025 — 08/09/2025: 2.80.0.0/14 announced by AS3243
- 04/08/2025 — 15/08/2025: 2.80.0.0/14 announced by AS3243
- 29/06/2025 — 03/08/2025: 2.80.0.0/14 announced by AS3243
- 30/04/2025 — 28/06/2025: 2.80.0.0/14 announced by AS3243
- 25/03/2025 — 29/04/2025: 2.80.0.0/14 announced by AS3243
- 13/03/2025 — 24/03/2025: 2.80.0.0/14 announced by AS3243
- 01/03/2025 — 12/03/2025: 2.80.0.0/14 announced by AS3243
- 17/02/2025 — 28/02/2025: 2.80.0.0/14 announced by AS3243
- 05/02/2025 — 16/02/2025: 2.80.0.0/14 announced by AS3243
- 19/12/2024 — 04/02/2025: 2.80.0.0/14 announced by AS3243
- 07/12/2024 — 18/12/2024: 2.80.0.0/14 announced by AS3243
- 13/11/2024 — 06/12/2024: 2.80.0.0/14 announced by AS3243
- 01/11/2024 — 12/11/2024: 2.80.0.0/14 announced by AS3243
- 20/10/2024 — 31/10/2024: 2.80.0.0/14 announced by AS3243
- 08/10/2024 — 19/10/2024: 2.80.0.0/14 announced by AS3243
- 26/09/2024 — 07/10/2024: 2.80.0.0/14 announced by AS3243
- 14/09/2024 — 25/09/2024: 2.80.0.0/14 announced by AS3243
- 09/08/2024 — 13/09/2024: 2.80.0.0/14 announced by AS3243
- 28/07/2024 — 08/08/2024: 2.80.0.0/14 announced by AS3243
- 22/06/2024 — 27/07/2024: 2.80.0.0/14 announced by AS3243
- 10/06/2024 — 21/06/2024: 2.80.0.0/14 announced by AS3243
- 29/05/2024 — 09/06/2024: 2.80.0.0/14 announced by AS3243
- 17/05/2024 — 28/05/2024: 2.80.0.0/14 announced by AS3243
- 23/04/2024 — 16/05/2024: 2.80.0.0/14 announced by AS3243
- 11/04/2024 — 22/04/2024: 2.80.0.0/14 announced by AS3243
- 30/03/2024 — 10/04/2024: 2.80.0.0/14 announced by AS3243
- 23/02/2024 — 29/03/2024: 2.80.0.0/14 announced by AS3243
- 11/02/2024 — 22/02/2024: 2.80.0.0/14 announced by AS3243
- 30/01/2024 — 10/02/2024: 2.80.0.0/14 announced by AS3243
- 18/01/2024 — 29/01/2024: 2.80.0.0/14 announced by AS3243
- 25/12/2023 — 17/01/2024: 2.80.0.0/14 announced by AS3243
- 13/12/2023 — 24/12/2023: 2.80.0.0/14 announced by AS3243
- 26/10/2023 — 12/12/2023: 2.80.0.0/14 announced by AS3243
- 27/08/2023 — 25/10/2023: 2.80.0.0/14 announced by AS3243
- 03/08/2023 — 26/08/2023: 2.80.0.0/14 announced by AS3243
- 22/07/2023 — 02/08/2023: 2.80.0.0/14 announced by AS3243
Abuse reputation — ALMC Shield
Not in the active feed
Recorded in the system but without enough cross-tenant reports right now (or delisted / under dispute).
2bans recorded by the network
1organisation
Technical data
| IP address | 2.82.222.57 |
| Version | IPv4 |
| Organisation (ASN) | RIPE Network Coordination Centre |
| Country | NL |
| Data center | No source: whois (0%) |
| AbuseIPDB confidence | 58% |
| AbuseIPDB total reports | 12 |
| First seen | 2026-09-07 23:11 |
| Last seen | 2026-09-07 23:27 |
Reported abuse types
plesk-modsecurity2 reports
Do you own this IP?
If it is listed by mistake, or the range is no longer yours, file a claim and we will review it. The form is on its Shield page, under the “Claim this IP” button.
Claim this IPWe will reply within 5-10 working days.
Analizar con otras herramientas
Is this IP giving you trouble?
We'll tell you within 24 h whether it's worth blocking, and how. No commitment, no sign-up.
