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: Ashburn

Region: Virginia

Country: United States

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 <<>> 68.139.5.144
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 27393
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;68.139.5.144.			IN	A

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

;; Query time: 104 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Dec 04 07:13:58 CST 2019
;; MSG SIZE  rcvd: 116
Host info
Host 144.5.139.68.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 144.5.139.68.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
185.176.222.99 attack
Port scan on 4 port(s): 3350 3370 3392 3393
2020-03-28 18:26:12
106.13.136.3 attack
(sshd) Failed SSH login from 106.13.136.3 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Mar 28 05:27:56 s1 sshd[27861]: Invalid user fgu from 106.13.136.3 port 48922
Mar 28 05:27:58 s1 sshd[27861]: Failed password for invalid user fgu from 106.13.136.3 port 48922 ssh2
Mar 28 05:43:07 s1 sshd[28145]: Invalid user xis from 106.13.136.3 port 35746
Mar 28 05:43:09 s1 sshd[28145]: Failed password for invalid user xis from 106.13.136.3 port 35746 ssh2
Mar 28 05:47:09 s1 sshd[28249]: Invalid user mbp from 106.13.136.3 port 33100
2020-03-28 18:09:33
101.91.242.119 attackspambots
2020-03-28T09:15:44.324530shield sshd\[16558\]: Invalid user hxj from 101.91.242.119 port 57600
2020-03-28T09:15:44.328156shield sshd\[16558\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.91.242.119
2020-03-28T09:15:45.576622shield sshd\[16558\]: Failed password for invalid user hxj from 101.91.242.119 port 57600 ssh2
2020-03-28T09:16:29.416449shield sshd\[16833\]: Invalid user bwf from 101.91.242.119 port 39856
2020-03-28T09:16:29.419976shield sshd\[16833\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.91.242.119
2020-03-28 18:09:59
189.130.173.217 attackspambots
Unauthorized connection attempt detected from IP address 189.130.173.217 to port 8000
2020-03-28 18:16:39
112.172.147.34 attackspambots
Mar 28 07:27:39 DAAP sshd[28203]: Invalid user wilmar from 112.172.147.34 port 11393
Mar 28 07:27:39 DAAP sshd[28203]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.172.147.34
Mar 28 07:27:39 DAAP sshd[28203]: Invalid user wilmar from 112.172.147.34 port 11393
Mar 28 07:27:41 DAAP sshd[28203]: Failed password for invalid user wilmar from 112.172.147.34 port 11393 ssh2
Mar 28 07:31:02 DAAP sshd[28255]: Invalid user whb from 112.172.147.34 port 9186
...
2020-03-28 18:05:02
218.159.169.3 attack
Unauthorized connection attempt detected from IP address 218.159.169.3 to port 23
2020-03-28 18:18:00
142.93.39.29 attackspam
SSH Brute-Force reported by Fail2Ban
2020-03-28 17:43:15
178.255.126.198 attackspambots
DATE:2020-03-28 08:50:20, IP:178.255.126.198, PORT:telnet Telnet brute force auth on honeypot server (honey-neo-dc)
2020-03-28 18:10:21
124.172.188.122 attack
Mar 25 19:55:22 server3 sshd[552]: Invalid user locco from 124.172.188.122 port 21744
Mar 25 19:55:22 server3 sshd[552]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.172.188.122
Mar 25 19:55:24 server3 sshd[552]: Failed password for invalid user locco from 124.172.188.122 port 21744 ssh2
Mar 25 19:55:24 server3 sshd[552]: Received disconnect from 124.172.188.122 port 21744:11: Bye Bye [preauth]
Mar 25 19:55:24 server3 sshd[552]: Disconnected from 124.172.188.122 port 21744 [preauth]
Mar 25 20:11:07 server3 sshd[1309]: Invalid user dz from 124.172.188.122 port 39411
Mar 25 20:11:07 server3 sshd[1309]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.172.188.122
Mar 25 20:11:09 server3 sshd[1309]: Failed password for invalid user dz from 124.172.188.122 port 39411 ssh2
Mar 25 20:11:09 server3 sshd[1309]: Received disconnect from 124.172.188.122 port 39411:11: Bye Bye [preauth]
Mar 25........
-------------------------------
2020-03-28 18:10:57
192.241.237.136 attackbotsspam
44818/tcp 5900/tcp 9042/tcp...
[2020-03-14/28]12pkt,9pt.(tcp),2pt.(udp)
2020-03-28 18:23:56
185.81.97.88 attack
IR_MDP583-RIPE_<177>1585367914 [1:2010935:3] ET SCAN Suspicious inbound to MSSQL port 1433 [Classification: Potentially Bad Traffic] [Priority: 2]:  {TCP} 185.81.97.88:44937
2020-03-28 18:04:19
130.180.193.73 attack
fail2ban
2020-03-28 18:09:10
194.26.29.120 attackspam
Mar 28 11:06:00 debian-2gb-nbg1-2 kernel: \[7649026.966584\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=194.26.29.120 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=40482 PROTO=TCP SPT=55499 DPT=4770 WINDOW=1024 RES=0x00 SYN URGP=0
2020-03-28 18:19:41
171.224.179.120 attackbots
20/3/27@23:47:37: FAIL: Alarm-Network address from=171.224.179.120
20/3/27@23:47:37: FAIL: Alarm-Network address from=171.224.179.120
...
2020-03-28 17:51:37
192.241.235.11 attackbotsspam
SSH brute-force attempt
2020-03-28 18:24:48

Recently Reported IPs

93.132.65.247 116.13.55.119 221.153.219.6 105.111.97.249
184.139.121.159 126.197.197.191 184.135.205.209 39.65.116.179
41.188.248.26 165.179.140.206 126.79.240.53 80.35.196.210
179.96.70.27 24.176.43.188 84.189.24.71 33.206.201.254
152.250.250.64 181.184.42.230 183.102.18.81 175.3.217.8