WHOIS Registry Details for IP 86.57.36.144
Information obtained from public network records.
Red
| NetRange | 86.0.0.0 - 86.255.255.255 |
| CIDR | 86.0.0.0/8 |
| NetName | 86-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 | 2004-04-01 |
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 86.57.36.144
Range 86.57.0.0/17
- 08/01/2010 — present: organization not on record · IR
Reverse DNS (PTR)
- 14/11/2026 — 14/11/2026: no reverse DNS
Route announcements (BGP)
- 11/08/2026 — 30/09/2026: 86.57.0.0/17 announced by AS43754
- 18/07/2026 — 10/08/2026: 86.57.0.0/17 announced by AS43754
- 06/07/2026 — 17/07/2026: 86.57.0.0/17 announced by AS43754
- 24/06/2026 — 05/07/2026: 86.57.0.0/17 announced by AS43754
- 07/05/2026 — 23/06/2026: 86.57.0.0/17 announced by AS43754
- 08/03/2026 — 06/05/2026: 86.57.0.0/17 announced by AS43754
- 24/02/2026 — 07/03/2026: 86.57.0.0/17 announced by AS43754
- 12/02/2026 — 23/02/2026: 86.57.0.0/17 announced by AS43754
- 19/01/2026 — 11/02/2026: 86.57.0.0/17 announced by AS43754
- 26/12/2025 — 18/01/2026: 86.57.0.0/17 announced by AS43754
- 02/12/2025 — 25/12/2025: 86.57.0.0/17 announced by AS43754
- 20/01/2019 — 31/01/2019: 86.0.0.0/8 announced by AS31554
- 22/09/2018 — 03/10/2018: 86.57.0.0/18 announced by AS50113
- 10/09/2018 — 21/09/2018: 86.57.0.0/18 announced by AS50113
- 29/08/2018 — 09/09/2018: 86.57.0.0/18 announced by AS50113
- 17/08/2018 — 28/08/2018: 86.57.0.0/18 announced by AS50113
- 23/05/2016 — 03/06/2016: 86.57.0.0/17 announced by AS44285
- 02/09/2015 — 07/10/2015: 86.57.0.0/17 announced by AS16322
- 21/08/2015 — 01/09/2015: 86.57.0.0/17 announced by AS16322
- 09/08/2015 — 20/08/2015: 86.57.0.0/17 announced by AS16322
- 28/07/2015 — 08/08/2015: 86.57.0.0/17 announced by AS16322
- 29/05/2015 — 27/07/2015: 86.57.0.0/17 announced by AS16322
- 06/03/2015 — 28/05/2015: 86.57.0.0/17 announced by AS16322
- 30/11/2014 — 05/03/2015: 86.57.0.0/17 announced by AS16322
- 18/11/2014 — 29/11/2014: 86.57.0.0/17 announced by AS16322
- 12/02/2010 — 23/02/2010: 86.57.0.0/17 announced by AS44285
- 19/01/2010 — 11/02/2010: 86.57.0.0/17 announced by AS44285
- 15/08/2007 — 26/08/2007: 86.0.0.0/7 announced by AS3352
- 15/03/2004 — 26/03/2004: 86.0.0.0/8 announced by AS19962
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).
1bans recorded by the network
1organisation
Technical data
| IP address | 86.57.36.144 |
| Version | IPv4 |
| Organisation (ASN) | RIPE Network Coordination Centre |
| Country | NL |
| Data center | No source: whois (0%) |
| AbuseIPDB confidence | 0% |
| AbuseIPDB total reports | 0 |
| First seen | 2026-11-14 22:47 |
| Last seen | 2026-11-14 22:47 |
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.