WHOIS Registry Details for IP 2a01:239:464:e700::1
- ALMC SECURITY S.L.U.
- Tools
- WHOIS Tool for 2a01:239:464:e700::1
Information obtained from public network records.
This IP address has been flagged as malicious (abuse). Take extra care.
Red
| Netname | DE-TECT-20061116 |
| Status | ALLOCATED-BY-RIR |
| Origin | AS8560 |
Organización
| Descr | IONOS-CLOUD-TXL |
| Org | ORG-SRA1-RIPE |
| Country | DE |
| Mnt by | RIPE-NCC-HM-MNT STRATO-RZG-MNT AS8560-MNT |
| Mnt lower | STRATO-RZG-MNT |
| Mnt routes | STRATO-RZG-MNT |
Contacto técnico
| Admin c | SH15342-RIPE SP20660-RIPE |
| Tech c | SH15342-RIPE SP20660-RIPE |
Registro
| Created | 2016-05-26T05:54:25Z 2025-09-12T08:40:59Z |
| Last modified | 2022-12-12T08:18:28Z 2025-09-12T08:40:59Z |
| Source | RIPE RIPE |
Información adicional
| Inet6num | 2a01:238::/29 |
| Notify | chmueller@cronon.net |
| Mnt domains | STRATO-RZG-MNT |
| Route6 | 2a01:239:400::/39 |
History of 2a01:239:464:e700::1
Range 2a01:238::/29
- 16/11/2006 — present: organization not on record · DE
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
No abuse reports on record
This IP is not listed in the ALMC Shield collaborative feed. That does not make it 100% safe, only that none of our nodes has reported it.
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.
