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

Region: Seoul

Country: South Korea

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

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

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

;; Query time: 25 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jul 16 08:22:04 CST 2020
;; MSG SIZE  rcvd: 116
Host info
Host 123.0.138.14.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 123.0.138.14.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
101.249.58.218 attackspam
spamhaus attack, whatever it is.
2019-07-21 03:35:29
188.128.39.133 attackbots
" "
2019-07-21 04:02:48
197.211.35.194 attack
Autoban   197.211.35.194 AUTH/CONNECT
2019-07-21 04:19:19
68.183.105.52 attack
FTP Brute-Force reported by Fail2Ban
2019-07-21 04:09:30
198.98.53.237 attackspam
Splunk® : port scan detected:
Jul 20 15:52:18 testbed kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=82:c6:52:d1:6e:53:c0:42:d0:39:2c:30:08:00 SRC=198.98.53.237 DST=104.248.11.191 LEN=44 TOS=0x08 PREC=0x00 TTL=246 ID=54321 PROTO=TCP SPT=51570 DPT=8088 WINDOW=65535 RES=0x00 SYN URGP=0
2019-07-21 04:18:59
170.244.69.100 attackspam
Jul 20 23:10:21 srv-4 sshd\[29830\]: Invalid user sgeadmin from 170.244.69.100
Jul 20 23:10:21 srv-4 sshd\[29830\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.244.69.100
Jul 20 23:10:23 srv-4 sshd\[29830\]: Failed password for invalid user sgeadmin from 170.244.69.100 port 8500 ssh2
...
2019-07-21 04:23:07
81.22.45.81 attack
Splunk® : port scan detected:
Jul 20 13:23:09 testbed kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=82:c6:52:d1:6e:53:c0:42:d0:39:2c:30:08:00 SRC=81.22.45.81 DST=104.248.11.191 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=53782 PROTO=TCP SPT=53873 DPT=3456 WINDOW=1024 RES=0x00 SYN URGP=0
2019-07-21 03:56:22
37.59.100.22 attackbotsspam
Jul 20 20:08:46 mail sshd\[2706\]: Failed password for invalid user ftpuser from 37.59.100.22 port 52168 ssh2
Jul 20 20:26:22 mail sshd\[2938\]: Invalid user mmm from 37.59.100.22 port 46833
Jul 20 20:26:22 mail sshd\[2938\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.59.100.22
...
2019-07-21 03:43:14
207.46.13.79 attackspambots
Automatic report - Banned IP Access
2019-07-21 04:18:39
190.143.39.211 attackbotsspam
Jul 20 20:31:30 microserver sshd[15703]: Invalid user max from 190.143.39.211 port 38004
Jul 20 20:31:30 microserver sshd[15703]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.143.39.211
Jul 20 20:31:33 microserver sshd[15703]: Failed password for invalid user max from 190.143.39.211 port 38004 ssh2
Jul 20 20:37:09 microserver sshd[16366]: Invalid user test2 from 190.143.39.211 port 36014
Jul 20 20:37:09 microserver sshd[16366]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.143.39.211
Jul 20 20:48:23 microserver sshd[19438]: Invalid user konrad from 190.143.39.211 port 60262
Jul 20 20:48:23 microserver sshd[19438]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.143.39.211
Jul 20 20:48:25 microserver sshd[19438]: Failed password for invalid user konrad from 190.143.39.211 port 60262 ssh2
Jul 20 20:54:03 microserver sshd[51543]: Invalid user raoul from 190.143.39.211 port 5826
2019-07-21 04:15:18
190.215.112.122 attack
Jul 20 20:10:02 MK-Soft-VM3 sshd\[18191\]: Invalid user li from 190.215.112.122 port 41827
Jul 20 20:10:02 MK-Soft-VM3 sshd\[18191\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.215.112.122
Jul 20 20:10:04 MK-Soft-VM3 sshd\[18191\]: Failed password for invalid user li from 190.215.112.122 port 41827 ssh2
...
2019-07-21 04:11:54
51.255.197.164 attack
2019-07-20T19:48:57.303058abusebot-6.cloudsearch.cf sshd\[20515\]: Invalid user emmanuel from 51.255.197.164 port 59374
2019-07-21 04:08:40
200.61.187.49 attackspam
445/tcp 445/tcp 445/tcp...
[2019-05-22/07-20]32pkt,1pt.(tcp)
2019-07-21 04:12:53
188.166.241.93 attackbotsspam
Jul 20 22:05:15 SilenceServices sshd[30727]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.241.93
Jul 20 22:05:17 SilenceServices sshd[30727]: Failed password for invalid user wei from 188.166.241.93 port 43916 ssh2
Jul 20 22:10:39 SilenceServices sshd[1464]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.241.93
2019-07-21 04:20:41
61.85.190.11 attackbotsspam
" "
2019-07-21 03:55:50

Recently Reported IPs

73.162.93.25 79.125.199.65 108.220.122.248 210.16.88.63
107.12.158.154 179.167.187.55 150.95.23.245 63.160.8.88
79.108.87.57 228.53.141.241 105.164.105.112 220.174.104.62
202.52.226.186 175.66.209.140 182.139.227.228 74.140.148.149
65.60.132.124 201.7.220.86 79.237.125.36 200.115.55.161