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

;; QUESTION SECTION:
;243.214.149.123.		IN	A

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

;; Query time: 269 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed May 18 13:41:17 CST 2022
;; MSG SIZE  rcvd: 108
Host info
Host 123.149.214.243.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.149.214.243.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
192.99.59.91 attackspam
Jun 22 10:05:21 mailserver sshd\[6739\]: Invalid user ts3bot from 192.99.59.91
...
2020-06-22 17:06:22
213.111.245.224 attackbotsspam
$f2bV_matches
2020-06-22 17:14:45
51.68.212.114 attackspambots
SSH authentication failure x 6 reported by Fail2Ban
...
2020-06-22 17:03:26
113.160.248.153 attack
1592797797 - 06/22/2020 05:49:57 Host: 113.160.248.153/113.160.248.153 Port: 445 TCP Blocked
2020-06-22 17:19:06
88.243.232.91 attackspam
firewall-block, port(s): 445/tcp
2020-06-22 17:11:03
109.234.39.56 attackspam
ssh brute force
2020-06-22 17:04:33
88.32.154.37 attack
Jun 22 02:05:30 ny01 sshd[8210]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=88.32.154.37
Jun 22 02:05:32 ny01 sshd[8210]: Failed password for invalid user billy from 88.32.154.37 port 50762 ssh2
Jun 22 02:09:00 ny01 sshd[8672]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=88.32.154.37
2020-06-22 17:01:20
122.225.130.74 attackspam
06/22/2020-04:35:15.859831 122.225.130.74 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2020-06-22 16:49:53
182.254.183.40 attackbotsspam
Jun 22 09:34:26 debian-2gb-nbg1-2 kernel: \[15069942.713531\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=182.254.183.40 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=237 ID=9093 PROTO=TCP SPT=56368 DPT=937 WINDOW=1024 RES=0x00 SYN URGP=0
2020-06-22 17:13:26
116.73.117.80 attackbotsspam
Automatic report - Banned IP Access
2020-06-22 17:00:11
118.175.90.242 attack
20/6/21@23:50:32: FAIL: Alarm-Network address from=118.175.90.242
...
2020-06-22 16:48:08
182.61.40.214 attackspam
Jun 22 00:50:17 vps46666688 sshd[15677]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.40.214
Jun 22 00:50:19 vps46666688 sshd[15677]: Failed password for invalid user efm from 182.61.40.214 port 59316 ssh2
...
2020-06-22 16:57:45
61.177.172.143 attackbotsspam
$f2bV_matches
2020-06-22 17:07:12
73.215.119.119 attackbots
Attempts against non-existent wp-login
2020-06-22 16:46:54
138.197.152.148 attack
 TCP (SYN) 138.197.152.148:56318 -> port 19579, len 44
2020-06-22 16:59:10

Recently Reported IPs

6.39.72.148 181.49.92.185 6.129.192.248 95.166.134.8
217.112.142.236 26.135.112.22 111.239.233.179 34.206.78.192
24.36.70.81 100.214.51.241 135.68.94.168 238.85.12.109
69.160.235.208 24.4.36.3 249.113.201.161 242.195.37.81
46.165.250.140 241.69.101.233 185.100.103.218 194.163.129.89