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: Kaohsiung City

Region: Kaohsiung

Country: Taiwan, China

Internet Service Provider: unknown

Hostname: unknown

Organization: Data Communication Business Group

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
IP Type Details Datetime
114.33.148.74 attackbots
Aug  8 14:15:28 debian-2gb-nbg1-2 kernel: \[19147374.678717\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=114.33.148.74 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=52 ID=46628 PROTO=TCP SPT=4604 DPT=9530 WINDOW=8191 RES=0x00 SYN URGP=0
2020-08-08 22:56:10
114.33.148.68 attackspambots
Port probing on unauthorized port 81
2020-06-12 00:26:25
114.33.148.23 attackbotsspam
Port probing on unauthorized port 8000
2020-06-08 12:09:30
114.33.148.74 attackbotsspam
Unauthorized connection attempt detected from IP address 114.33.148.74 to port 4567 [J]
2020-03-01 04:46:15
114.33.148.240 attackspambots
unauthorized connection attempt
2020-02-19 16:36:40
114.33.148.79 attackbots
Unauthorized connection attempt detected from IP address 114.33.148.79 to port 23 [J]
2020-01-25 18:40:04
114.33.148.203 attack
Too many connections or unauthorized access detected from Yankee banned ip
2019-09-04 08:31:08
114.33.148.79 attackbotsspam
1 attempts last 24 Hours
2019-08-29 00:29:37
Whois info:
b
Dig info:

; <<>> DiG 9.10.3-P4-Ubuntu <<>> 114.33.148.2
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 29560
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 1 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Thu Jun 27 14:30:06 CST 2019
;; MSG SIZE  rcvd: 116

Host info
2.148.33.114.in-addr.arpa has no PTR record
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

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

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
116.196.118.22 attackspambots
$f2bV_matches
2019-08-26 20:06:53
60.254.26.115 attackspam
Automatic report - Port Scan Attack
2019-08-26 19:55:24
61.7.190.253 attackspam
Lines containing failures of 61.7.190.253
Aug 26 05:18:30 shared09 sshd[26564]: Invalid user admin from 61.7.190.253 port 37664
Aug 26 05:18:30 shared09 sshd[26564]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.7.190.253
Aug 26 05:18:32 shared09 sshd[26564]: Failed password for invalid user admin from 61.7.190.253 port 37664 ssh2
Aug 26 05:18:32 shared09 sshd[26564]: Connection closed by invalid user admin 61.7.190.253 port 37664 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=61.7.190.253
2019-08-26 19:38:52
124.29.246.106 attack
Honeypot attack, port: 445, PTR: PTR record not found
2019-08-26 19:58:14
159.89.162.118 attack
Aug 26 09:37:10 minden010 sshd[2117]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.162.118
Aug 26 09:37:12 minden010 sshd[2117]: Failed password for invalid user mariadb from 159.89.162.118 port 53944 ssh2
Aug 26 09:41:47 minden010 sshd[4076]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.162.118
...
2019-08-26 19:55:06
177.69.213.236 attackspam
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.69.213.236  user=root
Failed password for root from 177.69.213.236 port 49384 ssh2
Invalid user winnie from 177.69.213.236 port 40162
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.69.213.236
Failed password for invalid user winnie from 177.69.213.236 port 40162 ssh2
2019-08-26 19:47:11
189.45.37.254 attackspambots
[SMB remote code execution attempt: port tcp/445]
*(RWIN=1024)(08261144)
2019-08-26 19:50:04
165.22.181.77 attackspambots
Aug 26 12:59:56 rpi sshd[25229]: Failed password for root from 165.22.181.77 port 40770 ssh2
2019-08-26 19:29:04
178.128.210.191 attack
Aug 26 12:43:36 rpi sshd[25069]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.210.191 
Aug 26 12:43:38 rpi sshd[25069]: Failed password for invalid user marco from 178.128.210.191 port 45434 ssh2
2019-08-26 19:08:46
174.138.6.146 attack
Aug 26 16:31:18 itv-usvr-01 sshd[19711]: Invalid user kush from 174.138.6.146
Aug 26 16:31:18 itv-usvr-01 sshd[19711]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.6.146
Aug 26 16:31:18 itv-usvr-01 sshd[19711]: Invalid user kush from 174.138.6.146
Aug 26 16:31:20 itv-usvr-01 sshd[19711]: Failed password for invalid user kush from 174.138.6.146 port 60936 ssh2
Aug 26 16:38:02 itv-usvr-01 sshd[19947]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.6.146  user=root
Aug 26 16:38:04 itv-usvr-01 sshd[19947]: Failed password for root from 174.138.6.146 port 43892 ssh2
2019-08-26 19:52:52
178.128.37.180 attackbots
Aug 26 13:37:09 vps647732 sshd[18597]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.37.180
Aug 26 13:37:10 vps647732 sshd[18597]: Failed password for invalid user admin from 178.128.37.180 port 52452 ssh2
...
2019-08-26 19:50:49
122.228.19.80 attackspambots
Port-scan: detected 102 distinct ports within a 24-hour window.
2019-08-26 19:10:09
51.81.18.73 attack
Aug 26 00:58:10 web1 sshd\[32397\]: Invalid user elisa from 51.81.18.73
Aug 26 00:58:10 web1 sshd\[32397\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.81.18.73
Aug 26 00:58:12 web1 sshd\[32397\]: Failed password for invalid user elisa from 51.81.18.73 port 22152 ssh2
Aug 26 01:02:32 web1 sshd\[343\]: Invalid user massimo from 51.81.18.73
Aug 26 01:02:32 web1 sshd\[343\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.81.18.73
2019-08-26 19:03:01
122.226.89.150 attackbots
Unauthorised access (Aug 26) SRC=122.226.89.150 LEN=52 TTL=113 ID=7490 DF TCP DPT=445 WINDOW=8192 SYN
2019-08-26 19:19:33
74.63.226.142 attackbotsspam
Aug 26 02:01:02 xtremcommunity sshd\[6296\]: Invalid user tomcat from 74.63.226.142 port 60200
Aug 26 02:01:02 xtremcommunity sshd\[6296\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=74.63.226.142
Aug 26 02:01:04 xtremcommunity sshd\[6296\]: Failed password for invalid user tomcat from 74.63.226.142 port 60200 ssh2
Aug 26 02:05:00 xtremcommunity sshd\[6493\]: Invalid user xavier from 74.63.226.142 port 50864
Aug 26 02:05:00 xtremcommunity sshd\[6493\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=74.63.226.142
...
2019-08-26 19:03:36

Recently Reported IPs

137.237.67.42 74.195.40.152 193.17.6.36 196.209.22.241
55.193.112.130 181.71.165.103 208.6.90.101 1.73.172.75
67.99.116.166 217.229.109.93 61.221.5.186 222.118.190.18
83.215.150.225 151.69.130.251 137.123.30.139 43.251.123.230
118.140.73.70 222.145.176.61 5.146.91.249 84.14.76.9