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

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

;; QUESTION SECTION:
;247.4.122.139.			IN	A

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

;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 19 04:36:58 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 139.122.4.247.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 139.122.4.247.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
61.54.41.147 attackbots
port scan and connect, tcp 23 (telnet)
2019-11-16 18:07:58
139.178.69.117 attack
DATE:2019-11-16 10:32:37, IP:139.178.69.117, PORT:ssh SSH brute force auth on honeypot server (honey-neo-dc)
2019-11-16 17:57:18
106.251.118.123 attackbots
$f2bV_matches
2019-11-16 17:43:58
122.235.250.120 attackbots
Lines containing failures of 122.235.250.120
Nov 14 10:19:58 MAKserver05 sshd[8660]: Invalid user hammersley from 122.235.250.120 port 36078
Nov 14 10:19:58 MAKserver05 sshd[8660]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.235.250.120 
Nov 14 10:20:00 MAKserver05 sshd[8660]: Failed password for invalid user hammersley from 122.235.250.120 port 36078 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=122.235.250.120
2019-11-16 18:20:49
51.75.24.200 attackbots
Automatic report - Banned IP Access
2019-11-16 17:46:43
106.12.17.43 attackspambots
Nov 16 09:26:27 microserver sshd[8068]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.17.43  user=root
Nov 16 09:26:29 microserver sshd[8068]: Failed password for root from 106.12.17.43 port 44124 ssh2
Nov 16 09:33:03 microserver sshd[8843]: Invalid user firdaus from 106.12.17.43 port 46748
Nov 16 09:33:03 microserver sshd[8843]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.17.43
Nov 16 09:33:05 microserver sshd[8843]: Failed password for invalid user firdaus from 106.12.17.43 port 46748 ssh2
Nov 16 10:18:25 microserver sshd[14999]: Invalid user guest from 106.12.17.43 port 34494
Nov 16 10:18:25 microserver sshd[14999]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.17.43
Nov 16 10:18:26 microserver sshd[14999]: Failed password for invalid user guest from 106.12.17.43 port 34494 ssh2
Nov 16 10:24:41 microserver sshd[15716]: Invalid user kloots from 106.12.17.43 por
2019-11-16 18:01:12
47.56.24.216 attack
CloudCIX Reconnaissance Scan Detected, PTR: PTR record not found
2019-11-16 17:51:10
178.62.36.116 attack
Nov 16 10:02:12 ns41 sshd[9370]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.62.36.116
2019-11-16 17:57:47
67.55.92.90 attackspambots
F2B blocked SSH bruteforcing
2019-11-16 17:56:56
178.128.221.162 attackspam
Nov 16 08:37:18 eventyay sshd[29390]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.221.162
Nov 16 08:37:20 eventyay sshd[29390]: Failed password for invalid user josimov from 178.128.221.162 port 52058 ssh2
Nov 16 08:41:03 eventyay sshd[29481]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.221.162
...
2019-11-16 18:21:34
106.12.45.108 attackbots
Nov 16 11:17:31 sso sshd[6377]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.45.108
Nov 16 11:17:33 sso sshd[6377]: Failed password for invalid user nuessle from 106.12.45.108 port 55596 ssh2
...
2019-11-16 18:19:19
222.186.175.148 attackbotsspam
2019-11-16T09:53:41.360350shield sshd\[24099\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.148  user=root
2019-11-16T09:53:42.919455shield sshd\[24099\]: Failed password for root from 222.186.175.148 port 46944 ssh2
2019-11-16T09:53:45.792611shield sshd\[24099\]: Failed password for root from 222.186.175.148 port 46944 ssh2
2019-11-16T09:53:49.075877shield sshd\[24099\]: Failed password for root from 222.186.175.148 port 46944 ssh2
2019-11-16T09:53:52.111394shield sshd\[24099\]: Failed password for root from 222.186.175.148 port 46944 ssh2
2019-11-16 18:04:03
222.186.175.167 attackbotsspam
Nov 16 12:19:06 sauna sshd[32439]: Failed password for root from 222.186.175.167 port 61212 ssh2
Nov 16 12:19:19 sauna sshd[32439]: error: maximum authentication attempts exceeded for root from 222.186.175.167 port 61212 ssh2 [preauth]
...
2019-11-16 18:21:59
139.199.158.14 attackbotsspam
Nov 16 09:31:23 localhost sshd\[2507\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.158.14  user=backup
Nov 16 09:31:24 localhost sshd\[2507\]: Failed password for backup from 139.199.158.14 port 53509 ssh2
Nov 16 09:36:34 localhost sshd\[2561\]: Invalid user egil from 139.199.158.14 port 43767
...
2019-11-16 17:43:36
171.244.140.174 attackspam
Nov 16 10:31:39 dedicated sshd[30676]: Invalid user ld from 171.244.140.174 port 14128
2019-11-16 17:49:42

Recently Reported IPs

192.2.8.164 237.223.32.187 146.26.147.49 195.242.110.44
90.142.80.236 126.57.85.181 217.65.153.3 152.53.58.191
246.229.191.170 68.221.63.136 146.68.127.152 170.87.203.54
173.35.165.171 135.171.29.64 170.223.32.181 157.51.26.214
124.5.54.243 211.47.190.157 101.203.171.11 75.39.34.97