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

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

;; QUESTION SECTION:
;113.200.148.55.			IN	A

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

;; Query time: 49 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Apr 04 16:38:17 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 55.148.200.113.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 55.148.200.113.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
115.79.117.53 attackbots
Unauthorized connection attempt from IP address 115.79.117.53 on Port 445(SMB)
2019-09-07 18:50:19
177.38.194.5 attackspambots
Attempted WordPress login: "GET /wp-login.php"
2019-09-07 18:54:01
117.208.13.199 attackbotsspam
Sniffing for wp-login
2019-09-07 19:09:26
185.130.56.71 attackspam
WordPress login Brute force / Web App Attack on client site.
2019-09-07 19:01:56
178.62.9.122 attack
WordPress wp-login brute force :: 178.62.9.122 0.128 BYPASS [07/Sep/2019:20:52:03  1000] [censored_1] "POST /wp-login.php HTTP/1.1" 200 3972 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-09-07 19:06:34
218.98.40.148 attackspambots
Sep  7 11:06:04 MK-Soft-VM4 sshd\[5011\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.98.40.148  user=root
Sep  7 11:06:06 MK-Soft-VM4 sshd\[5011\]: Failed password for root from 218.98.40.148 port 41452 ssh2
Sep  7 11:06:09 MK-Soft-VM4 sshd\[5011\]: Failed password for root from 218.98.40.148 port 41452 ssh2
...
2019-09-07 19:46:21
2.236.242.44 attackbotsspam
Sep  7 13:13:51 mail sshd\[3170\]: Invalid user mine from 2.236.242.44 port 50253
Sep  7 13:13:51 mail sshd\[3170\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=2.236.242.44
Sep  7 13:13:54 mail sshd\[3170\]: Failed password for invalid user mine from 2.236.242.44 port 50253 ssh2
Sep  7 13:20:39 mail sshd\[3993\]: Invalid user devops from 2.236.242.44 port 52751
Sep  7 13:20:39 mail sshd\[3993\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=2.236.242.44
2019-09-07 19:42:40
46.101.142.99 attack
Sep  7 01:35:05 php2 sshd\[23918\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.142.99  user=mysql
Sep  7 01:35:08 php2 sshd\[23918\]: Failed password for mysql from 46.101.142.99 port 36058 ssh2
Sep  7 01:39:07 php2 sshd\[24386\]: Invalid user tom from 46.101.142.99
Sep  7 01:39:07 php2 sshd\[24386\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.142.99
Sep  7 01:39:08 php2 sshd\[24386\]: Failed password for invalid user tom from 46.101.142.99 port 50744 ssh2
2019-09-07 19:40:08
185.10.68.221 attack
Fail2Ban Ban Triggered
2019-09-07 19:21:09
35.200.42.221 attackbots
Sep  7 01:19:36 aiointranet sshd\[9879\]: Invalid user oracle from 35.200.42.221
Sep  7 01:19:36 aiointranet sshd\[9879\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.42.200.35.bc.googleusercontent.com
Sep  7 01:19:38 aiointranet sshd\[9879\]: Failed password for invalid user oracle from 35.200.42.221 port 53478 ssh2
Sep  7 01:29:04 aiointranet sshd\[10656\]: Invalid user admin from 35.200.42.221
Sep  7 01:29:04 aiointranet sshd\[10656\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.42.200.35.bc.googleusercontent.com
2019-09-07 19:29:37
113.193.191.132 attackspam
Sep  7 01:04:20 lcprod sshd\[14660\]: Invalid user test7 from 113.193.191.132
Sep  7 01:04:20 lcprod sshd\[14660\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.193.191.132
Sep  7 01:04:22 lcprod sshd\[14660\]: Failed password for invalid user test7 from 113.193.191.132 port 51316 ssh2
Sep  7 01:10:13 lcprod sshd\[15262\]: Invalid user 123qwe from 113.193.191.132
Sep  7 01:10:13 lcprod sshd\[15262\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.193.191.132
2019-09-07 19:10:37
114.5.12.186 attackbotsspam
Sep  7 12:52:17 core sshd[14984]: Invalid user admin from 114.5.12.186 port 56303
Sep  7 12:52:20 core sshd[14984]: Failed password for invalid user admin from 114.5.12.186 port 56303 ssh2
...
2019-09-07 19:09:55
142.169.129.243 attackspambots
19/9/7@06:52:20: FAIL: IoT-Telnet address from=142.169.129.243
...
2019-09-07 19:08:50
124.156.103.34 attack
Sep  7 13:21:36 plex sshd[17396]: Invalid user deploy from 124.156.103.34 port 47480
2019-09-07 19:34:11
218.98.26.174 attack
Sep  7 13:22:32 v22018053744266470 sshd[27216]: Failed password for root from 218.98.26.174 port 26365 ssh2
Sep  7 13:22:43 v22018053744266470 sshd[27232]: Failed password for root from 218.98.26.174 port 12356 ssh2
...
2019-09-07 19:46:45

Recently Reported IPs

113.200.114.192 113.200.153.61 113.200.174.12 113.200.174.36
113.200.244.246 113.200.245.163 113.200.46.184 113.200.52.5
113.200.73.10 113.201.132.72 113.31.145.93 113.31.165.6
113.35.233.180 172.171.63.140 113.35.41.45 113.35.99.49
113.38.194.165 113.38.217.83 113.39.159.148 113.4.141.130