Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: United Kingdom of Great Britain and Northern Ireland (the)

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 2.100.159.104
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 49749
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;2.100.159.104.			IN	A

;; AUTHORITY SECTION:
.			30	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2025021800 1800 900 604800 86400

;; Query time: 68 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 22:01:49 CST 2025
;; MSG SIZE  rcvd: 106
Host info
104.159.100.2.in-addr.arpa domain name pointer host-2-100-159-104.as13285.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
104.159.100.2.in-addr.arpa	name = host-2-100-159-104.as13285.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
49.88.112.113 attack
2019-12-05T21:09:14.780063abusebot.cloudsearch.cf sshd\[27229\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.113  user=root
2019-12-06 05:14:10
51.89.166.45 attackspambots
Dec  5 13:05:25 ws24vmsma01 sshd[72383]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.89.166.45
Dec  5 13:05:27 ws24vmsma01 sshd[72383]: Failed password for invalid user sikri from 51.89.166.45 port 46590 ssh2
...
2019-12-06 04:52:34
101.187.39.74 attackspambots
$f2bV_matches
2019-12-06 04:43:03
118.26.128.202 attackbotsspam
Dec  5 19:15:14 XXX sshd[21940]: Invalid user ftpuser from 118.26.128.202 port 42952
2019-12-06 04:53:11
54.37.158.218 attackbots
Dec  5 21:27:56 * sshd[17641]: Failed password for root from 54.37.158.218 port 44687 ssh2
2019-12-06 04:47:40
106.12.108.32 attackspam
Dec  5 21:35:18 vps666546 sshd\[25952\]: Invalid user chisheng from 106.12.108.32 port 59284
Dec  5 21:35:18 vps666546 sshd\[25952\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.108.32
Dec  5 21:35:20 vps666546 sshd\[25952\]: Failed password for invalid user chisheng from 106.12.108.32 port 59284 ssh2
Dec  5 21:41:10 vps666546 sshd\[26296\]: Invalid user terrans from 106.12.108.32 port 38258
Dec  5 21:41:10 vps666546 sshd\[26296\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.108.32
...
2019-12-06 04:50:56
106.52.115.36 attackbots
web-1 [ssh_2] SSH Attack
2019-12-06 04:38:33
206.189.166.172 attackspambots
$f2bV_matches
2019-12-06 04:37:48
148.70.246.130 attackspam
Dec  5 15:57:57 ny01 sshd[13428]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.246.130
Dec  5 15:57:59 ny01 sshd[13428]: Failed password for invalid user mysql from 148.70.246.130 port 44738 ssh2
Dec  5 16:04:07 ny01 sshd[14335]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.246.130
2019-12-06 05:22:26
180.250.115.98 attackbots
Dec  5 20:28:10 hosting sshd[20241]: Invalid user admin123467 from 180.250.115.98 port 36159
...
2019-12-06 04:57:58
182.61.58.131 attackspambots
Dec  5 21:50:59 sbg01 sshd[17915]: Failed password for root from 182.61.58.131 port 36282 ssh2
Dec  5 22:06:01 sbg01 sshd[18026]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.58.131
Dec  5 22:06:03 sbg01 sshd[18026]: Failed password for invalid user norment from 182.61.58.131 port 46770 ssh2
2019-12-06 05:11:35
46.101.27.6 attackspambots
Dec  5 23:53:25 *** sshd[5373]: Failed password for invalid user david from 46.101.27.6 port 44198 ssh2
2019-12-06 04:37:18
88.191.58.21 attackbotsspam
Automatic report - Port Scan Attack
2019-12-06 05:13:47
106.12.34.226 attack
Aug  7 16:16:27 microserver sshd[35377]: Invalid user bcbackup from 106.12.34.226 port 41274
Aug  7 16:16:27 microserver sshd[35377]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.34.226
Aug  7 16:16:30 microserver sshd[35377]: Failed password for invalid user bcbackup from 106.12.34.226 port 41274 ssh2
Aug  7 16:19:23 microserver sshd[35620]: Invalid user kt from 106.12.34.226 port 32958
Aug  7 16:19:23 microserver sshd[35620]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.34.226
Dec  5 15:00:13 microserver sshd[12547]: Invalid user schibig from 106.12.34.226 port 42362
Dec  5 15:00:13 microserver sshd[12547]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.34.226
Dec  5 15:00:14 microserver sshd[12547]: Failed password for invalid user schibig from 106.12.34.226 port 42362 ssh2
Dec  5 15:07:37 microserver sshd[13702]: pam_unix(sshd:auth): authentication failure; lo
2019-12-06 04:42:29
178.219.50.205 attackbots
12/05/2019-16:04:10.680121 178.219.50.205 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-12-06 05:18:03

Recently Reported IPs

92.8.79.9 35.238.147.73 176.243.114.112 239.3.157.184
87.183.56.104 140.42.106.254 31.174.17.197 51.28.239.237
52.23.188.48 154.22.140.237 136.227.16.128 127.104.209.122
178.31.250.138 38.187.235.25 116.49.9.55 243.181.112.234
7.15.212.215 15.80.70.245 200.126.54.245 209.144.175.75