2. Tools
  3. WHOIS Tool for 5.202.241.42
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.

WHOIS Registry Details for IP 5.202.241.42

Information obtained from public network records.

Red

NetRange
5.0.0.0 - 5.255.255.255
CIDR
5.0.0.0/8
NetName
RIPE-5
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
2010-11-30

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 5.202.241.42

Range 5.202.0.0/16

  • 29/08/2012 — present: organization not on record · IR

Reverse DNS (PTR)

  • 07/09/2026 — 07/09/2026: mail.kiyanisatis.com

Route announcements (BGP)

  • 11/08/2026 — 03/09/2026: 5.202.0.0/16 announced by AS49100
  • 18/07/2026 — 10/08/2026: 5.202.0.0/16 announced by AS49100
  • 24/06/2026 — 17/07/2026: 5.202.0.0/16 announced by AS49100
  • 07/05/2026 — 23/06/2026: 5.202.0.0/16 announced by AS49100
  • 13/04/2026 — 06/05/2026: 5.202.0.0/16 announced by AS49100
  • 01/04/2026 — 12/04/2026: 5.202.0.0/16 announced by AS49100
  • 08/03/2026 — 31/03/2026: 5.202.0.0/16 announced by AS49100
  • 24/02/2026 — 07/03/2026: 5.202.0.0/16 announced by AS49100
  • 12/02/2026 — 23/02/2026: 5.202.0.0/16 announced by AS49100
  • 31/01/2026 — 11/02/2026: 5.202.0.0/16 announced by AS49100
  • 19/01/2026 — 30/01/2026: 5.202.0.0/16 announced by AS49100
  • 26/12/2025 — 18/01/2026: 5.202.0.0/16 announced by AS49100
  • 02/12/2025 — 25/12/2025: 5.202.0.0/16 announced by AS49100
  • 20/11/2025 — 01/12/2025: 5.202.0.0/16 announced by AS49100
  • 27/10/2025 — 19/11/2025: 5.202.0.0/16 announced by AS49100
  • 09/09/2025 — 26/10/2025: 5.202.0.0/16 announced by AS49100
  • 16/08/2025 — 08/09/2025: 5.202.0.0/16 announced by AS49100
  • 04/08/2025 — 15/08/2025: 5.202.0.0/16 announced by AS49100
  • 23/07/2025 — 03/08/2025: 5.202.0.0/16 announced by AS49100
  • 30/04/2025 — 22/07/2025: 5.202.0.0/16 announced by AS49100
  • 25/03/2025 — 29/04/2025: 5.202.0.0/16 announced by AS49100
  • 13/03/2025 — 24/03/2025: 5.202.0.0/16 announced by AS49100
  • 01/03/2025 — 12/03/2025: 5.202.0.0/16 announced by AS49100
  • 17/02/2025 — 28/02/2025: 5.202.0.0/16 announced by AS49100
  • 05/02/2025 — 16/02/2025: 5.202.0.0/16 announced by AS49100
  • 19/12/2024 — 04/02/2025: 5.202.0.0/16 announced by AS49100
  • 07/12/2024 — 18/12/2024: 5.202.0.0/16 announced by AS49100
  • 13/11/2024 — 06/12/2024: 5.202.0.0/16 announced by AS49100
  • 01/11/2024 — 12/11/2024: 5.202.0.0/16 announced by AS49100
  • 20/10/2024 — 31/10/2024: 5.202.0.0/16 announced by AS49100
  • 08/10/2024 — 19/10/2024: 5.202.0.0/16 announced by AS49100
  • 26/09/2024 — 07/10/2024: 5.202.0.0/16 announced by AS49100
  • 14/09/2024 — 25/09/2024: 5.202.0.0/16 announced by AS49100
  • 09/08/2024 — 13/09/2024: 5.202.0.0/16 announced by AS49100
  • 22/06/2024 — 08/08/2024: 5.202.0.0/16 announced by AS49100
  • 10/06/2024 — 21/06/2024: 5.202.0.0/16 announced by AS49100
  • 23/04/2024 — 09/06/2024: 5.202.0.0/16 announced by AS49100
  • 11/04/2024 — 22/04/2024: 5.202.0.0/16 announced by AS49100
  • 30/03/2024 — 10/04/2024: 5.202.0.0/16 announced by AS49100
  • 23/02/2024 — 29/03/2024: 5.202.0.0/16 announced by AS49100
  • 18/01/2024 — 22/02/2024: 5.202.0.0/16 announced by AS49100
  • 25/12/2023 — 17/01/2024: 5.202.0.0/16 announced by AS49100
  • 13/12/2023 — 24/12/2023: 5.202.0.0/16 announced by AS49100
  • 26/10/2023 — 12/12/2023: 5.202.0.0/16 announced by AS49100
  • 27/08/2023 — 25/10/2023: 5.202.0.0/16 announced by AS49100
  • 03/08/2023 — 26/08/2023: 5.202.0.0/16 announced by AS49100
  • 22/07/2023 — 02/08/2023: 5.202.0.0/16 announced by AS49100
  • 28/06/2023 — 21/07/2023: 5.202.0.0/16 announced by AS49100
  • 16/06/2023 — 27/06/2023: 5.202.0.0/16 announced by AS49100
  • 04/06/2023 — 15/06/2023: 5.202.0.0/16 announced by AS49100

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 address5.202.241.42
VersionIPv4
Organisation (ASN)RIPE Network Coordination Centre
CountryNL
Data center No source: whois (0%)
AbuseIPDB confidence52%
AbuseIPDB total reports8
First seen2026-09-07 17:57
Last seen2026-09-07 17:57

Reported abuse types

  • sshd1 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

Concerned about the security of your website or business?

At ALMC we design secure websites, AI chatbots and automations that protect and grow your business. Free proposal in 24h.

Get your quote in 2 minutes
CiberseguridadChatbot IADesarrollo WebAutomatizaciónCompresor Imágenes