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

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

;; QUESTION SECTION:
;13.50.140.106.			IN	A

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

;; Query time: 20 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 12 21:13:49 CST 2022
;; MSG SIZE  rcvd: 106
Host info
106.140.50.13.in-addr.arpa domain name pointer ec2-13-50-140-106.eu-north-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
106.140.50.13.in-addr.arpa	name = ec2-13-50-140-106.eu-north-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
76.10.157.36 attackspambots
SSH login attempts.
2020-02-17 19:22:03
140.213.59.254 attackbotsspam
[Mon Feb 17 11:54:56.501374 2020] [:error] [pid 11333:tid 140577555363584] [client 140.213.59.254:42402] [client 140.213.59.254] ModSecurity: Access denied with code 403 (phase 4). Pattern match "^5\\\\d{2}$" at RESPONSE_STATUS. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/RESPONSE-950-DATA-LEAKAGES.conf"] [line "118"] [id "950100"] [msg "The Application Returned a 500-Level Status Code"] [data "Matched Data: 500 found within RESPONSE_STATUS: 500"] [severity "ERROR"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-disclosure"] [tag "WASCTC/WASC-13"] [tag "OWASP_TOP_10/A6"] [tag "PCI/6.5.6"] [tag "paranoia-level/2"] [hostname "karangploso.jatim.bmkg.go.id"] [uri "/index.php/prakiraan-iklim/prakiraan-bulanan/prakiraan-hujan-bulanan/prakiraan-curah-hujan-bulanan/555557608-prakiraan-bulanan-curah-hujan-bulan-januari-tahun-2020-update-dari-analisis-bulan-september-2019"] [unique_id "XkocoCKsjobM@NabR@cILAAAAAE"], refe
...
2020-02-17 19:54:13
36.233.29.134 attackbots
Attempt to attack host OS, exploiting network vulnerabilities, on 17-02-2020 04:55:11.
2020-02-17 19:30:24
123.181.121.230 attack
SSH login attempts.
2020-02-17 19:54:29
112.85.42.180 attackspam
2020-02-05T11:12:57.106Z CLOSE host=112.85.42.180 port=19162 fd=4 time=20.015 bytes=9
...
2020-02-17 19:52:11
98.136.96.92 attack
SSH login attempts.
2020-02-17 19:23:19
122.176.44.163 attackbots
Feb 16 18:51:13 sachi sshd\[18110\]: Invalid user oracle from 122.176.44.163
Feb 16 18:51:13 sachi sshd\[18110\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.176.44.163
Feb 16 18:51:16 sachi sshd\[18110\]: Failed password for invalid user oracle from 122.176.44.163 port 42900 ssh2
Feb 16 18:55:17 sachi sshd\[18530\]: Invalid user ts3server from 122.176.44.163
Feb 16 18:55:17 sachi sshd\[18530\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.176.44.163
2020-02-17 19:17:52
197.248.34.106 attackbotsspam
Brute force attempt
2020-02-17 19:22:25
106.54.48.29 attack
Feb 17 10:26:25 tuxlinux sshd[2473]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.48.29  user=root
Feb 17 10:26:26 tuxlinux sshd[2473]: Failed password for root from 106.54.48.29 port 38498 ssh2
Feb 17 10:26:25 tuxlinux sshd[2473]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.48.29  user=root
Feb 17 10:26:26 tuxlinux sshd[2473]: Failed password for root from 106.54.48.29 port 38498 ssh2
Feb 17 10:40:34 tuxlinux sshd[2791]: Invalid user guy from 106.54.48.29 port 38258
...
2020-02-17 19:44:53
119.235.50.26 attackbots
IP was detected trying to Brute-Force SSH, FTP, Web Apps, Port-Scan or Hacking.
2020-02-17 19:46:46
106.12.49.150 attack
21 attempts against mh-ssh on cloud
2020-02-17 19:57:11
41.141.70.23 attack
1581915294 - 02/17/2020 11:54:54 Host: 41.141.70.23/41.141.70.23 Port: 23 TCP Blocked
...
2020-02-17 19:59:54
218.92.0.168 attackbots
Feb 17 12:22:44 dedicated sshd[21888]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.168  user=root
Feb 17 12:22:46 dedicated sshd[21888]: Failed password for root from 218.92.0.168 port 2508 ssh2
2020-02-17 19:33:35
93.61.134.60 attackbotsspam
Feb 17 05:54:59 localhost sshd\[17230\]: Invalid user xiu from 93.61.134.60 port 46982
Feb 17 05:54:59 localhost sshd\[17230\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=93.61.134.60
Feb 17 05:55:01 localhost sshd\[17230\]: Failed password for invalid user xiu from 93.61.134.60 port 46982 ssh2
2020-02-17 19:48:49
84.22.42.115 attackspambots
port scan and connect, tcp 1433 (ms-sql-s)
2020-02-17 19:37:40

Recently Reported IPs

172.67.219.84 106.13.154.203 62.93.26.56 9.23.49.213
85.16.110.242 207.88.111.62 219.35.42.97 33.131.138.225
152.247.177.244 32.71.156.5 3.101.139.243 117.202.13.165
38.106.83.43 196.28.137.249 177.213.72.181 34.170.190.141
167.80.200.58 136.83.87.30 112.234.186.173 84.115.239.6