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

;; QUESTION SECTION:
;13.49.36.142.			IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 05:09:50 CST 2022
;; MSG SIZE  rcvd: 105
Host info
142.36.49.13.in-addr.arpa domain name pointer ec2-13-49-36-142.eu-north-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
142.36.49.13.in-addr.arpa	name = ec2-13-49-36-142.eu-north-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
51.91.157.101 attackspam
Invalid user lkh from 51.91.157.101 port 53036
2020-05-25 07:21:59
180.76.181.47 attack
May 24 17:51:40 ny01 sshd[24917]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.181.47
May 24 17:51:42 ny01 sshd[24917]: Failed password for invalid user www1 from 180.76.181.47 port 36960 ssh2
May 24 17:54:57 ny01 sshd[25351]: Failed password for root from 180.76.181.47 port 34678 ssh2
2020-05-25 07:42:34
93.171.5.244 attackbots
 TCP (SYN) 93.171.5.244:55467 -> port 8167, len 44
2020-05-25 07:37:52
110.49.71.249 attack
May 24 22:28:36 sip sshd[389378]: Failed password for root from 110.49.71.249 port 61365 ssh2
May 24 22:29:40 sip sshd[389410]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.49.71.249  user=root
May 24 22:29:42 sip sshd[389410]: Failed password for root from 110.49.71.249 port 13414 ssh2
...
2020-05-25 07:34:01
180.76.177.194 attack
k+ssh-bruteforce
2020-05-25 07:38:09
167.172.69.52 attackbotsspam
2020-05-24T20:22:55.014151dmca.cloudsearch.cf sshd[10016]: Invalid user ospite from 167.172.69.52 port 35442
2020-05-24T20:22:55.021985dmca.cloudsearch.cf sshd[10016]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.172.69.52
2020-05-24T20:22:55.014151dmca.cloudsearch.cf sshd[10016]: Invalid user ospite from 167.172.69.52 port 35442
2020-05-24T20:22:57.097102dmca.cloudsearch.cf sshd[10016]: Failed password for invalid user ospite from 167.172.69.52 port 35442 ssh2
2020-05-24T20:26:27.672575dmca.cloudsearch.cf sshd[10364]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.172.69.52  user=root
2020-05-24T20:26:29.852843dmca.cloudsearch.cf sshd[10364]: Failed password for root from 167.172.69.52 port 34978 ssh2
2020-05-24T20:29:49.475006dmca.cloudsearch.cf sshd[10749]: Invalid user uucp from 167.172.69.52 port 34520
...
2020-05-25 07:25:32
80.234.45.49 attackbotsspam
Automatic report - Banned IP Access
2020-05-25 07:30:40
41.225.18.218 attackspam
Invalid user geier from 41.225.18.218 port 32965
2020-05-25 07:44:49
59.120.227.134 attackspam
May 24 01:01:26: Invalid user jgl from 59.120.227.134 port 53662
2020-05-25 07:35:52
116.232.253.10 attackbotsspam
05/24/2020-16:29:26.225048 116.232.253.10 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2020-05-25 07:45:59
157.245.122.248 attackspam
May 24 18:28:31 s158375 sshd[27434]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.245.122.248
2020-05-25 07:32:53
117.121.214.50 attack
2020-05-24T21:51:15.635466abusebot-4.cloudsearch.cf sshd[13864]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.121.214.50  user=root
2020-05-24T21:51:17.640015abusebot-4.cloudsearch.cf sshd[13864]: Failed password for root from 117.121.214.50 port 55550 ssh2
2020-05-24T21:55:09.484478abusebot-4.cloudsearch.cf sshd[14195]: Invalid user prueba from 117.121.214.50 port 34012
2020-05-24T21:55:09.490274abusebot-4.cloudsearch.cf sshd[14195]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.121.214.50
2020-05-24T21:55:09.484478abusebot-4.cloudsearch.cf sshd[14195]: Invalid user prueba from 117.121.214.50 port 34012
2020-05-24T21:55:11.288456abusebot-4.cloudsearch.cf sshd[14195]: Failed password for invalid user prueba from 117.121.214.50 port 34012 ssh2
2020-05-24T21:59:02.162817abusebot-4.cloudsearch.cf sshd[14483]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=1
...
2020-05-25 07:18:24
122.51.154.172 attackbots
SASL PLAIN auth failed: ruser=...
2020-05-25 07:33:31
139.162.65.76 attack
 TCP (SYN) 139.162.65.76:38962 -> port 102, len 44
2020-05-25 07:47:46
218.104.225.140 attackspambots
May 25 00:52:27  sshd\[15969\]: User root from 218.104.225.140 not allowed because not listed in AllowUsersMay 25 00:52:28  sshd\[15969\]: Failed password for invalid user root from 218.104.225.140 port 53416 ssh2
...
2020-05-25 07:39:08

Recently Reported IPs

13.49.36.100 13.49.6.100 13.49.38.160 13.49.63.217
13.49.7.187 13.49.82.62 13.49.63.100 13.49.8.159
13.49.85.185 13.49.85.167 118.172.148.93 13.49.86.155
13.49.86.196 13.49.89.86 13.49.87.94 13.51.104.196
13.49.92.252 13.49.99.63 13.49.87.221 13.51.101.197