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: North Bergen

Region: New Jersey

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:
IP Type Details Datetime
167.99.149.11 attack
Automatic report generated by Wazuh
2020-10-10 03:56:19
167.99.149.11 attack
can 167.99.149.11 [09/Oct/2020:18:09:47 "-" "POST /wp-login.php 200 5780
167.99.149.11 [09/Oct/2020:18:42:33 "-" "GET /wp-login.php 200 9378
167.99.149.11 [09/Oct/2020:18:42:40 "-" "POST /wp-login.php 200 9495
2020-10-09 19:52:36
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 167.99.149.249
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 41466
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;167.99.149.249.			IN	A

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

;; Query time: 22 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Oct 21 17:19:31 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 249.149.99.167.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 249.149.99.167.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
31.44.80.185 attack
Unauthorized connection attempt detected from IP address 31.44.80.185 to port 3389
2019-12-23 02:22:34
51.89.36.26 attackspambots
" "
2019-12-23 02:01:12
81.22.45.150 attack
Dec 22 18:50:54 debian-2gb-nbg1-2 kernel: \[689804.184489\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=81.22.45.150 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=63634 PROTO=TCP SPT=55190 DPT=3390 WINDOW=1024 RES=0x00 SYN URGP=0
2019-12-23 01:58:09
70.190.21.240 attackspambots
12/22/2019-09:49:48.382931 70.190.21.240 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-12-23 02:17:15
106.12.36.42 attackbotsspam
2019-12-22T17:45:09.944021shield sshd\[21688\]: Invalid user kaiserauer from 106.12.36.42 port 38138
2019-12-22T17:45:09.948419shield sshd\[21688\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.36.42
2019-12-22T17:45:11.698350shield sshd\[21688\]: Failed password for invalid user kaiserauer from 106.12.36.42 port 38138 ssh2
2019-12-22T17:51:32.160471shield sshd\[23940\]: Invalid user kavitha from 106.12.36.42 port 39484
2019-12-22T17:51:32.164615shield sshd\[23940\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.36.42
2019-12-23 02:11:02
203.205.50.54 attack
Unauthorized connection attempt detected from IP address 203.205.50.54 to port 445
2019-12-23 01:44:55
188.140.135.242 attackbotsspam
Unauthorized connection attempt detected from IP address 188.140.135.242 to port 445
2019-12-23 02:07:01
185.175.93.27 attackspam
12/22/2019-18:48:23.571938 185.175.93.27 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2019-12-23 01:54:32
51.158.24.203 attackspambots
MultiHost/MultiPort Probe, Scan, Hack -
2019-12-23 01:53:42
78.29.32.122 attackbots
SPAM Delivery Attempt
2019-12-23 02:03:02
213.182.101.187 attack
Dec 22 22:34:06 gw1 sshd[3620]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.182.101.187
Dec 22 22:34:08 gw1 sshd[3620]: Failed password for invalid user web from 213.182.101.187 port 47488 ssh2
...
2019-12-23 01:47:47
178.33.45.156 attack
Dec 22 18:44:25 silence02 sshd[5163]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.33.45.156
Dec 22 18:44:27 silence02 sshd[5163]: Failed password for invalid user sudir from 178.33.45.156 port 54062 ssh2
Dec 22 18:50:33 silence02 sshd[5401]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.33.45.156
2019-12-23 01:51:05
183.230.199.54 attack
Dec 22 14:06:45 firewall sshd[2777]: Failed password for invalid user mysql from 183.230.199.54 port 52577 ssh2
Dec 22 14:13:20 firewall sshd[2918]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.230.199.54  user=root
Dec 22 14:13:22 firewall sshd[2918]: Failed password for root from 183.230.199.54 port 47563 ssh2
...
2019-12-23 01:44:38
193.29.15.86 attackbotsspam
193.29.15.86 was recorded 12 times by 8 hosts attempting to connect to the following ports: 123. Incident counter (4h, 24h, all-time): 12, 14, 14
2019-12-23 02:13:33
160.202.161.233 attackbots
firewall-block, port(s): 445/tcp
2019-12-23 01:49:06

Recently Reported IPs

1.9.53.136 65.43.151.200 56.159.75.48 185.176.18.8
138.254.158.36 10.230.190.31 173.162.18.100 172.25.141.43
247.49.106.3 243.74.248.177 36.238.58.68 8.156.10.90
236.160.180.168 13.190.81.1 47.195.210.201 124.66.143.237
71.11.77.70 146.70.236.128 129.99.220.199 105.73.3.7