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

;; QUESTION SECTION:
;103.133.138.55.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 08 11:16:19 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 55.138.133.103.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.138.133.103.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
218.92.0.191 attackspam
Nov 22 18:56:56 dcd-gentoo sshd[28064]: User root from 218.92.0.191 not allowed because none of user's groups are listed in AllowGroups
Nov 22 18:57:00 dcd-gentoo sshd[28064]: error: PAM: Authentication failure for illegal user root from 218.92.0.191
Nov 22 18:56:56 dcd-gentoo sshd[28064]: User root from 218.92.0.191 not allowed because none of user's groups are listed in AllowGroups
Nov 22 18:57:00 dcd-gentoo sshd[28064]: error: PAM: Authentication failure for illegal user root from 218.92.0.191
Nov 22 18:56:56 dcd-gentoo sshd[28064]: User root from 218.92.0.191 not allowed because none of user's groups are listed in AllowGroups
Nov 22 18:57:00 dcd-gentoo sshd[28064]: error: PAM: Authentication failure for illegal user root from 218.92.0.191
Nov 22 18:57:00 dcd-gentoo sshd[28064]: Failed keyboard-interactive/pam for invalid user root from 218.92.0.191 port 40832 ssh2
...
2019-11-23 02:09:30
103.47.14.206 attackbotsspam
port scan/probe/communication attempt; port 23
2019-11-23 02:10:46
80.211.137.52 attackbots
Nov 18 14:49:55 sanyalnet-cloud-vps4 sshd[22942]: Connection from 80.211.137.52 port 50568 on 64.137.160.124 port 23
Nov 18 14:49:57 sanyalnet-cloud-vps4 sshd[22942]: Address 80.211.137.52 maps to host52-137-211-80.serverdedicati.aruba.hostname, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Nov 18 14:49:57 sanyalnet-cloud-vps4 sshd[22942]: Invalid user szikla from 80.211.137.52
Nov 18 14:49:57 sanyalnet-cloud-vps4 sshd[22942]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.211.137.52 
Nov 18 14:49:59 sanyalnet-cloud-vps4 sshd[22942]: Failed password for invalid user szikla from 80.211.137.52 port 50568 ssh2
Nov 18 14:49:59 sanyalnet-cloud-vps4 sshd[22942]: Received disconnect from 80.211.137.52: 11: Bye Bye [preauth]
Nov 18 14:53:43 sanyalnet-cloud-vps4 sshd[23048]: Connection from 80.211.137.52 port 59922 on 64.137.160.124 port 23
Nov 18 14:53:44 sanyalnet-cloud-vps4 sshd[23048]: Address 80.211.137.52........
-------------------------------
2019-11-23 01:40:24
69.167.210.118 attack
Nov 22 17:35:16 thevastnessof sshd[16172]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.167.210.118
...
2019-11-23 01:51:55
185.236.229.23 attackbots
Attempted to connect 3 times to port 5555 TCP
2019-11-23 01:42:19
180.76.157.48 attackspam
Automatic report - Banned IP Access
2019-11-23 01:43:58
95.154.88.70 attackbots
2019-11-22 15:54:43,211 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 95.154.88.70
2019-11-22 16:28:42,958 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 95.154.88.70
2019-11-22 17:03:20,222 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 95.154.88.70
2019-11-22 17:45:10,896 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 95.154.88.70
2019-11-22 18:28:02,587 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 95.154.88.70
...
2019-11-23 01:59:39
78.154.188.59 attackspambots
Automatic report - Port Scan Attack
2019-11-23 01:55:36
125.164.232.60 attack
Unauthorized connection attempt from IP address 125.164.232.60 on Port 445(SMB)
2019-11-23 01:53:14
202.184.49.17 attackbotsspam
SSH bruteforce
2019-11-23 02:05:37
5.196.217.177 attackspam
Nov 22 18:00:41  postfix/smtpd: warning: unknown[5.196.217.177]: SASL LOGIN authentication failed
2019-11-23 02:05:12
115.231.231.3 attackspam
Nov 22 17:58:17 legacy sshd[3402]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.231.231.3
Nov 22 17:58:19 legacy sshd[3402]: Failed password for invalid user harm from 115.231.231.3 port 38338 ssh2
Nov 22 18:03:06 legacy sshd[3575]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.231.231.3
...
2019-11-23 02:10:29
179.107.84.18 attack
Unauthorized connection attempt from IP address 179.107.84.18 on Port 445(SMB)
2019-11-23 01:42:36
222.190.143.206 attack
SSH Brute Force, server-1 sshd[4948]: Failed password for invalid user 100 from 222.190.143.206 port 9137 ssh2
2019-11-23 01:45:28
193.1.209.152 attackbotsspam
BURG,WP GET /wp-login.php
2019-11-23 02:15:08

Recently Reported IPs

209.85.218.43 117.201.207.246 197.210.85.45 64.227.174.170
218.161.65.121 54.241.140.118 164.90.232.169 197.37.131.177
116.75.244.177 222.121.158.124 111.37.252.167 81.68.188.228
177.157.19.103 41.139.11.231 27.147.131.138 142.11.229.49
77.45.245.18 114.119.144.212 65.108.0.150 211.36.141.225