WHOIS Registry Details for IP 2a01:239:4af:2c00::1
Information obtained from public network records.
Red
| NetRange | 2A00:: - 2A0F:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF |
| CIDR | 2A00::/12 |
| NetName | EU-ZZ-2A00 |
| 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 | 2006-10-03 |
Información adicional
| OriginAS | |
| City | Amsterdam |
| StateProv | |
| PostalCode | 1001EB |
| ReferralServer | whois.ripe.net |
| OrgTechHandle | RNO29-ARIN |
| OrgTechName | RIPE NCC Operations |
| OrgAbuseHandle | ABUSE3850-ARIN |
| OrgAbuseName | Abuse Contact |
History of 2a01:239:4af:2c00::1
Range 2a01:238::/29
- 16/11/2006 — present: organization not on record · DE
Reverse DNS (PTR)
- 10/10/2026 — 10/10/2026: no reverse DNS
Route announcements (BGP)
- 06/07/2026 — 10/09/2026: 2a01:238::/29 announced by AS6724
- 06/07/2026 — 10/09/2026: 2a01:239::/32 announced by AS8560
- 25/04/2026 — 05/07/2026: 2a01:239::/32 announced by AS8560
- 25/04/2026 — 05/07/2026: 2a01:238::/29 announced by AS6724
- 13/04/2026 — 24/04/2026: 2a01:239::/32 announced by AS8560
- 13/04/2026 — 24/04/2026: 2a01:238::/29 announced by AS6724
- 20/03/2026 — 12/04/2026: 2a01:239::/32 announced by AS8560
- 20/03/2026 — 12/04/2026: 2a01:238::/29 announced by AS6724
- 24/02/2026 — 19/03/2026: 2a01:238::/29 announced by AS6724
- 24/02/2026 — 19/03/2026: 2a01:239::/32 announced by AS8560
- 12/02/2026 — 23/02/2026: 2a01:238::/29 announced by AS6724
- 12/02/2026 — 23/02/2026: 2a01:239::/32 announced by AS8560
- 19/01/2026 — 11/02/2026: 2a01:238::/29 announced by AS6724
- 19/01/2026 — 11/02/2026: 2a01:239::/32 announced by AS8560
- 07/01/2026 — 18/01/2026: 2a01:238::/29 announced by AS6724
- 07/01/2026 — 18/01/2026: 2a01:239::/32 announced by AS8560
- 26/12/2025 — 06/01/2026: 2a01:239::/32 announced by AS8560
- 26/12/2025 — 06/01/2026: 2a01:238::/29 announced by AS6724
- 02/12/2025 — 25/12/2025: 2a01:239::/32 announced by AS8560
- 02/12/2025 — 25/12/2025: 2a01:238::/29 announced by AS6724
- 20/11/2025 — 01/12/2025: 2a01:238::/29 announced by AS6724
- 20/11/2025 — 01/12/2025: 2a01:239::/32 announced by AS8560
- 21/09/2025 — 19/11/2025: 2a01:239::/32 announced by AS8560
- 21/09/2025 — 19/11/2025: 2a01:238::/29 announced by AS6724
- 04/08/2025 — 20/09/2025: 2a01:238::/29 announced by AS6724
- 04/08/2025 — 20/09/2025: 2a01:239::/32 announced by AS8560
- 23/07/2025 — 03/08/2025: 2a01:238::/29 announced by AS6724
- 23/07/2025 — 03/08/2025: 2a01:239::/32 announced by AS8560
- 11/07/2025 — 22/07/2025: 2a01:239::/32 announced by AS8560
- 11/07/2025 — 22/07/2025: 2a01:238::/29 announced by AS6724
- 29/06/2025 — 10/07/2025: 2a01:238::/29 announced by AS6724
- 29/06/2025 — 10/07/2025: 2a01:239::/32 announced by AS8560
- 05/06/2025 — 28/06/2025: 2a01:238::/29 announced by AS6724
- 05/06/2025 — 28/06/2025: 2a01:239::/32 announced by AS8560
- 12/05/2025 — 04/06/2025: 2a01:239::/32 announced by AS8560
- 12/05/2025 — 04/06/2025: 2a01:238::/29 announced by AS6724
- 30/04/2025 — 11/05/2025: 2a01:238::/29 announced by AS6724
- 30/04/2025 — 11/05/2025: 2a01:239::/32 announced by AS8560
- 18/04/2025 — 29/04/2025: 2a01:238::/29 announced by AS6724
- 18/04/2025 — 29/04/2025: 2a01:239::/32 announced by AS8560
- 25/03/2025 — 17/04/2025: 2a01:238::/29 announced by AS6724
- 25/03/2025 — 17/04/2025: 2a01:239::/32 announced by AS8560
- 13/03/2025 — 24/03/2025: 2a01:239::/32 announced by AS8560
- 13/03/2025 — 24/03/2025: 2a01:238::/29 announced by AS6724
- 01/03/2025 — 12/03/2025: 2a01:239::/32 announced by AS8560
- 01/03/2025 — 12/03/2025: 2a01:238::/29 announced by AS6724
- 17/02/2025 — 28/02/2025: 2a01:238::/29 announced by AS6724
- 17/02/2025 — 28/02/2025: 2a01:239::/32 announced by AS8560
- 24/01/2025 — 16/02/2025: 2a01:238::/29 announced by AS6724
- 24/01/2025 — 16/02/2025: 2a01:239::/32 announced by AS8560
Abuse reputation — ALMC Shield
In the global abuse feed
The network recorded 1 ban of this address, all from a single organisation.
1bans recorded by the network
1organisation
2026-10-10first seen
Technical data
| IP address | 2a01:239:4af:2c00::1 |
| Version | IPv6 |
| Organisation (ASN) | RIPE Network Coordination Centre |
| Country | NL |
| Data center | Sí source: multiple (75%) |
| AbuseIPDB confidence | 27% |
| AbuseIPDB total reports | 11 |
| First seen | 2026-10-10 16:09 |
| Last seen | 2026-10-10 16:13 |
Reported abuse types
plesk-modsecurity1 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.