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: United States

Internet Service Provider: Verizon

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

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

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

;; Query time: 180 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 16 05:20:24 CST 2020
;; MSG SIZE  rcvd: 117
Host info
;; connection timed out; no servers could be reached
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
*** Can't find 118.156.1.149.in-addr.arpa.: No answer

Authoritative answers can be found from:

Related IP info:
Related comments:
IP Type Details Datetime
209.141.62.184 attackspambots
$f2bV_matches
2020-02-27 03:43:03
2.180.21.179 attack
Honeypot attack, port: 81, PTR: PTR record not found
2020-02-27 03:36:48
210.12.49.162 attack
Feb 26 17:45:34 server sshd\[21277\]: Invalid user jxw from 210.12.49.162
Feb 26 17:45:34 server sshd\[21277\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.12.49.162 
Feb 26 17:45:35 server sshd\[21277\]: Failed password for invalid user jxw from 210.12.49.162 port 33837 ssh2
Feb 26 17:56:18 server sshd\[23026\]: Invalid user steve from 210.12.49.162
Feb 26 17:56:18 server sshd\[23026\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.12.49.162 
...
2020-02-27 03:28:30
210.116.114.1 attack
$f2bV_matches
2020-02-27 03:29:33
129.28.35.148 attackbots
Lines containing failures of 129.28.35.148
Feb 26 17:37:57 shared02 sshd[2093]: Invalid user qq from 129.28.35.148 port 49130
Feb 26 17:37:57 shared02 sshd[2093]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.28.35.148
Feb 26 17:37:59 shared02 sshd[2093]: Failed password for invalid user qq from 129.28.35.148 port 49130 ssh2
Feb 26 17:38:00 shared02 sshd[2093]: Received disconnect from 129.28.35.148 port 49130:11: Bye Bye [preauth]
Feb 26 17:38:00 shared02 sshd[2093]: Disconnected from invalid user qq 129.28.35.148 port 49130 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=129.28.35.148
2020-02-27 03:36:17
210.177.54.141 attackbotsspam
$f2bV_matches
2020-02-27 03:24:44
207.154.234.102 attack
Automatic report - Banned IP Access
2020-02-27 03:52:23
94.25.30.27 attackspam
Automatic report - Port Scan Attack
2020-02-27 03:34:05
207.46.13.53 attackspambots
Automatic report - Banned IP Access
2020-02-27 03:30:12
134.175.85.79 attack
Automatic report - SSH Brute-Force Attack
2020-02-27 03:50:24
208.113.200.55 attackspambots
$f2bV_matches
2020-02-27 03:48:28
185.143.221.170 attack
2020-02-26 19:47:53 kernel: DROP IN=ppp0 OUT= MAC= SRC=185.143.221.170
2020-02-27 03:49:13
120.92.93.12 attackspam
suspicious action Wed, 26 Feb 2020 10:34:25 -0300
2020-02-27 03:59:23
206.81.4.235 attackspambots
$f2bV_matches
2020-02-27 03:58:36
70.95.63.117 attackbotsspam
Automatic report - Port Scan Attack
2020-02-27 03:39:48

Recently Reported IPs

212.72.62.152 100.195.107.19 109.225.99.212 31.27.172.193
84.40.150.95 114.171.190.231 39.225.178.73 119.224.243.195
188.184.241.89 45.170.231.121 164.146.135.105 62.23.68.14
114.79.173.41 174.48.16.75 186.66.68.188 98.14.229.62
61.90.42.30 162.78.69.7 87.146.146.140 118.37.22.192