WHOIS Registry Details for IP 92.217.29.10

  1. ALMC SECURITY S.L.U.
  2. Tools
  3. WHOIS Tool for 92.217.29.10
Tools
Ocultar Latest IPs Viewed Mostrar Latest IPs Viewed

Tools

Quickly access our network and diagnostics tools.

Latest IPs Viewed

Explore recent IPs on our secure platform. Access WHOIS data to see managing organizations and protect your network with ALMC Security.

Information obtained from public network records.

Red

NetRange
92.0.0.0 - 92.255.255.255
CIDR
92.0.0.0/8
NetName
92-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

OrgAbuseEmailabuse@ripe.net
OrgAbusePhone
+31205354444
OrgTechEmailhostmaster@ripe.net
OrgTechPhone
+31 20 535 4444

Registro

Updated
2025-02-10
2013-07-29
RegDate
2007-03-27

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 92.217.29.10

Range 92.216.0.0/14

  • 17/10/2007 — present: organization not on record · DE

Range 92.208.0.0 – 92.219.255.255

  • 25/08/2026 — present: DE-ARCOR-20071017 · DE · AS3209

Reverse DNS (PTR)

  • 05/10/2026 — 05/10/2026: ipservice-092-217-029-010.092.217.pools.vodafone-ip.de

Route announcements (BGP)

  • 21/04/2013 — 02/05/2013: 92.192.0.0/11 announced by AS20676
  • 09/04/2013 — 20/04/2013: 92.192.0.0/11 announced by AS20676
  • 28/03/2013 — 08/04/2013: 92.192.0.0/11 announced by AS20676
  • 16/03/2013 — 27/03/2013: 92.192.0.0/11 announced by AS20676
  • 04/03/2013 — 15/03/2013: 92.192.0.0/11 announced by AS20676
  • 20/02/2013 — 03/03/2013: 92.192.0.0/11 announced by AS20676
  • 08/02/2013 — 19/02/2013: 92.192.0.0/11 announced by AS20676
  • 27/01/2013 — 07/02/2013: 92.192.0.0/11 announced by AS20676
  • 15/01/2013 — 26/01/2013: 92.192.0.0/11 announced by AS20676
  • 03/01/2013 — 14/01/2013: 92.192.0.0/11 announced by AS20676
  • 22/12/2012 — 02/01/2013: 92.192.0.0/11 announced by AS20676
  • 10/12/2012 — 21/12/2012: 92.192.0.0/11 announced by AS20676
  • 28/11/2012 — 09/12/2012: 92.192.0.0/11 announced by AS20676
  • 16/11/2012 — 27/11/2012: 92.192.0.0/11 announced by AS20676
  • 04/11/2012 — 15/11/2012: 92.192.0.0/11 announced by AS20676
  • 11/10/2012 — 03/11/2012: 92.192.0.0/11 announced by AS20676
  • 29/09/2012 — 10/10/2012: 92.192.0.0/11 announced by AS20676
  • 17/09/2012 — 28/09/2012: 92.192.0.0/11 announced by AS20676
  • 07/07/2012 — 16/09/2012: 92.192.0.0/11 announced by AS20676
  • 25/06/2012 — 06/07/2012: 92.192.0.0/11 announced by AS20676
  • 13/06/2012 — 24/06/2012: 92.192.0.0/11 announced by AS20676
  • 20/05/2012 — 12/06/2012: 92.192.0.0/11 announced by AS20676
  • 08/05/2012 — 19/05/2012: 92.192.0.0/11 announced by AS20676
  • 26/04/2012 — 07/05/2012: 92.192.0.0/11 announced by AS20676
  • 14/04/2012 — 25/04/2012: 92.192.0.0/11 announced by AS20676
  • 21/03/2012 — 13/04/2012: 92.192.0.0/11 announced by AS20676
  • 21/01/2012 — 20/03/2012: 92.192.0.0/11 announced by AS20676
  • 04/12/2011 — 08/01/2012: 92.192.0.0/11 announced by AS20676
  • 10/11/2011 — 03/12/2011: 92.192.0.0/11 announced by AS20676
  • 17/10/2011 — 09/11/2011: 92.192.0.0/11 announced by AS20676
  • 23/09/2011 — 16/10/2011: 92.192.0.0/11 announced by AS20676
  • 18/08/2011 — 22/09/2011: 92.192.0.0/11 announced by AS20676
  • 25/07/2011 — 17/08/2011: 92.192.0.0/11 announced by AS20676
  • 26/05/2011 — 24/07/2011: 92.192.0.0/11 announced by AS20676
  • 14/05/2011 — 25/05/2011: 92.192.0.0/11 announced by AS20676
  • 15/03/2011 — 13/05/2011: 92.192.0.0/11 announced by AS20676
  • 07/02/2011 — 14/03/2011: 92.192.0.0/11 announced by AS20676
  • 02/01/2011 — 06/02/2011: 92.192.0.0/11 announced by AS20676
  • 21/12/2010 — 01/01/2011: 92.192.0.0/11 announced by AS20676
  • 27/11/2010 — 20/12/2010: 92.192.0.0/11 announced by AS20676
  • 15/11/2010 — 26/11/2010: 92.192.0.0/11 announced by AS20676
  • 03/11/2010 — 14/11/2010: 92.192.0.0/11 announced by AS20676
  • 28/09/2010 — 02/11/2010: 92.192.0.0/11 announced by AS20676
  • 04/09/2010 — 27/09/2010: 92.192.0.0/11 announced by AS20676
  • 18/07/2010 — 03/09/2010: 92.192.0.0/11 announced by AS20676
  • 24/06/2010 — 17/07/2010: 92.192.0.0/11 announced by AS20676
  • 07/05/2010 — 23/06/2010: 92.192.0.0/11 announced by AS20676
  • 13/04/2010 — 06/05/2010: 92.192.0.0/11 announced by AS20676
  • 24/02/2010 — 12/04/2010: 92.192.0.0/11 announced by AS20676
  • 12/02/2010 — 23/02/2010: 92.192.0.0/11 announced by AS20676

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 address92.217.29.10
VersionIPv4
Organisation (ASN)RIPE Network Coordination Centre
CountryNL
Data center No source: whois (0%)
AbuseIPDB confidence15%
AbuseIPDB total reports2
First seen2026-10-05 07:25
Last seen2026-10-05 07:43

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 IP

We will reply within 5-10 working days.

Analizar con otras herramientas

Reverse Lookup Geolocate IP ASN Lookup Abuse Shield

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.

CiberseguridadChatbot IADesarrollo WebAutomatizaciónCompresor Imágenes