Skip to main content
IT BIBLESign in

Honeypot

We run decoy servers on the open internet. Nothing real is on them, and nobody has a reason to connect, so everything that does is a scan or an attack. This page shows what they try, with addresses and guesses redacted. Paying members can get the raw data for their own tools. You can also download the free blocklist or check whether an address has attacked us.

292
Different addresses, last 24 hours
51
Countries they came from
8,954
Login attempts
8,531
Logins the decoy accepted
New York City
$ attacks --last 24h292 different addresses from 51 countries, hitting New York City

Where they came from

Different addresses in the last 24 hours, by country

  1. US80
  2. GB34
  3. NL20
  4. BE17
  5. CN14
  6. KR7
  7. IN7
  8. UA7
  9. RO6
  10. PK6

Whose networks

Top network owners with their network numbers (ASNs), last 24 hours

Which cities

Shown only when 10 or more different addresses came from one, over 7 days. City is approximate: it is where an address is registered, often far from the machine.

  1. Brussels, BE17
  2. Amsterdam, NL15
  3. Manchester, GB10
  4. Cedar Knolls, US10

What they go after

Events by service the decoy pretends to run

  1. mssql18,429
  2. ssh13,280
  3. telnet2,703
  4. rdp1,724
  5. smb587
  6. http513
  7. winrm80

Usernames they guess

Listed only when 25 or more different addresses tried one, over 7 days, so nobody's own name appears. Names that look personal are cut short.

  1. admin34
  2. root32

Passwords they guess

Under the same rule, with most of each password hidden. The count is how many different addresses tried it.

  1. a****28

How far they got

Events by stage of an attack, last 24 hours

  1. access17,485
  2. discovery9,143
  3. recon292
  4. delivery2

Bots and people

Judged from how fast and how regularly the input arrives

  1. Automated (a script)6,384
  2. Looks like a person typing132

Different addresses per day, last 1 days

Join free to see 90 days

The trend appears once a couple of days have been counted.

A sample of what the sensors see

Shown 15 minutes late. Addresses are cut to their first three parts, usernames to two letters, and passwords are never shown.

WhenWhatServiceFromNetworkUsername
Login accepted by the decoyssh203.99.53.x PKNayatel (Pvt) Ltdad***
Login attemptssh203.99.53.x PKNayatel (Pvt) Ltdad***
Login accepted by the decoyssh203.99.53.x PKNayatel (Pvt) Ltdad***
Login attemptssh203.99.53.x PKNayatel (Pvt) Ltdad***
Login attemptssh203.99.53.x PKNayatel (Pvt) Ltdro***
Login attemptssh203.99.53.x PKNayatel (Pvt) Ltdad***
New attackerwinrm203.99.53.x PKNayatel (Pvt) Ltd
Login accepted by the decoyssh193.46.255.x ROUnmanaged Ltdad***
Login attemptssh193.46.255.x ROUnmanaged Ltdad***
Login accepted by the decoytelnet102.215.13.x KESPRINKVILLE NETWORKS LIMITEDro***
Login attempttelnet102.215.13.x KESPRINKVILLE NETWORKS LIMITEDro***
Login attempttelnet102.215.13.x KESPRINKVILLE NETWORKS LIMITEDro***
Login attempttelnet102.215.13.x KESPRINKVILLE NETWORKS LIMITEDro***
New attackertelnet102.215.13.x KESPRINKVILLE NETWORKS LIMITED
New attackerssh199.165.159.x USThe Shadowserver Foundation, Inc.

What we collect, and who sees what

Every event a sensor sees is stored for 90 days; daily counts are kept for good. Attackers type whatever they like, so we treat all of it as untrusted and never show it unredacted on this page.

WhatExampleOn this pageSigned in (free)Paying members (API)
The event
When, what happened and which service2026-11-21 10:04 UTC, login attempt, sshCounts, and a sample 15 minutes lateSameEvery event, as it happens
Where it came from
Address203.0.113.42Last part hidden: 203.0.113.x (the free blocklist lists full addresses that attacked repeatedly)SameFull address
CountryNetherlandsMap and top countriesSameOn every event
City, region, postal code, time zoneAmsterdam, North Holland, 1012Top cities, only when 10 or more different addresses came from oneSameOn every event, with how accurate it is
Network ownerExample Hosting B.V.Top 10 owners, with network numbers (each has a page)SameOn every event
What they tried
UsernamerootTop names, only when 25 or more different addresses tried one. Samples show two lettersTop 100 under the same ruleEvery username, with the address and time
Passwordhu******Top ones under the same rule, with most of each hiddenSameEvery password, in full
Files they tried to leavea1b2c3… (a hash), 48 KBCountsCountsThe hash and size
Session length41 seconds, 7 eventsNot shownNot shownOn every session
Never collected or shared
Commands typed, web requests and what they carried, file names, recordingsKept on the sensor onlyNoNoNo

Put the numbers on your own page

A small badge with the live number of different addresses that attacked us in the last 24 hours, for a README or a blog. Choices and shields.io

Different addresses that attacked the honeypot in the last 24 hours

[![Honeypot attackers](https://itbible.org/tools/honeypot/badge.svg)](https://itbible.org/tools/honeypot)

Join free for longer lists

Signed-in members see the top 100 usernames and passwords (under the same privacy rules), and 90 days of trend. A plan adds the raw data through an API.