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

;; QUESTION SECTION:
;49.142.208.141.			IN	A

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

;; Query time: 36 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 17:45:01 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 141.208.142.49.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 141.208.142.49.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
173.249.2.122 attack
Connection by 173.249.2.122 on port: 6379 got caught by honeypot at 11/5/2019 7:16:02 AM
2019-11-05 16:41:27
3.82.172.95 attack
TCP Port Scanning
2019-11-05 16:23:44
221.3.104.204 attackspambots
TCP Port Scanning
2019-11-05 16:19:47
110.138.227.126 attackbotsspam
DATE:2019-11-05 07:15:33, IP:110.138.227.126, PORT:telnet Telnet brute force auth on honeypot server (honey-neo-dc-bis)
2019-11-05 16:07:01
116.196.83.174 attackspam
Nov  5 07:28:02 MK-Soft-Root1 sshd[17168]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.196.83.174 
Nov  5 07:28:05 MK-Soft-Root1 sshd[17168]: Failed password for invalid user applmgr from 116.196.83.174 port 59892 ssh2
...
2019-11-05 16:25:00
83.97.20.46 attackbotsspam
Connection by 83.97.20.46 on port: 587 got caught by honeypot at 11/5/2019 5:27:47 AM
2019-11-05 16:40:01
222.186.173.180 attackbotsspam
2019-11-05T08:33:19.015284abusebot.cloudsearch.cf sshd\[1392\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.180  user=root
2019-11-05 16:34:08
49.234.44.48 attack
Nov  5 09:52:58 microserver sshd[19062]: Invalid user qy321321 from 49.234.44.48 port 54341
Nov  5 09:52:58 microserver sshd[19062]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.44.48
Nov  5 09:53:00 microserver sshd[19062]: Failed password for invalid user qy321321 from 49.234.44.48 port 54341 ssh2
Nov  5 09:56:40 microserver sshd[19651]: Invalid user discordbot123 from 49.234.44.48 port 41127
Nov  5 09:56:40 microserver sshd[19651]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.44.48
Nov  5 10:08:30 microserver sshd[21145]: Invalid user j0b from 49.234.44.48 port 57974
Nov  5 10:08:30 microserver sshd[21145]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.44.48
Nov  5 10:08:32 microserver sshd[21145]: Failed password for invalid user j0b from 49.234.44.48 port 57974 ssh2
Nov  5 10:12:18 microserver sshd[21777]: Invalid user websync from 49.234.44.48 port 44763
No
2019-11-05 16:27:27
104.161.34.78 attackbotsspam
Nov  5 08:37:30 server3 sshd[2807]: reveeclipse mapping checking getaddrinfo for . [104.161.34.78] failed - POSSIBLE BREAK-IN ATTEMPT!
Nov  5 08:37:30 server3 sshd[2807]: Invalid user ubnt from 104.161.34.78
Nov  5 08:37:30 server3 sshd[2807]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.161.34.78
Nov  5 08:37:32 server3 sshd[2807]: Failed password for invalid user ubnt from 104.161.34.78 port 59825 ssh2
Nov  5 08:37:32 server3 sshd[2807]: Received disconnect from 104.161.34.78: 11: Bye Bye [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=104.161.34.78
2019-11-05 16:36:29
59.63.208.54 attack
Nov  5 09:06:55 server sshd\[9801\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.63.208.54  user=root
Nov  5 09:06:57 server sshd\[9801\]: Failed password for root from 59.63.208.54 port 47940 ssh2
Nov  5 09:22:56 server sshd\[13652\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.63.208.54  user=root
Nov  5 09:22:59 server sshd\[13652\]: Failed password for root from 59.63.208.54 port 38572 ssh2
Nov  5 09:27:50 server sshd\[14920\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.63.208.54  user=root
...
2019-11-05 16:37:02
187.177.130.238 attackbots
Automatic report - Port Scan Attack
2019-11-05 16:42:37
13.251.170.198 attackbots
RDP Bruteforce
2019-11-05 16:13:56
195.154.211.33 attack
Input Traffic from this IP, but critial abuseconfidencescore
2019-11-05 16:18:13
209.97.178.115 attackbotsspam
Nov  5 06:27:53 ms-srv sshd[33391]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=209.97.178.115  user=root
Nov  5 06:27:55 ms-srv sshd[33391]: Failed password for invalid user root from 209.97.178.115 port 59016 ssh2
2019-11-05 16:32:15
91.121.142.225 attack
Nov  4 22:16:19 web1 sshd\[24104\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.121.142.225  user=root
Nov  4 22:16:21 web1 sshd\[24104\]: Failed password for root from 91.121.142.225 port 33712 ssh2
Nov  4 22:20:29 web1 sshd\[24477\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.121.142.225  user=root
Nov  4 22:20:31 web1 sshd\[24477\]: Failed password for root from 91.121.142.225 port 43918 ssh2
Nov  4 22:24:47 web1 sshd\[24823\]: Invalid user ubnt from 91.121.142.225
Nov  4 22:24:47 web1 sshd\[24823\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.121.142.225
2019-11-05 16:36:43

Recently Reported IPs

49.144.194.135 49.143.14.70 49.144.207.221 49.144.232.119
49.145.135.26 49.145.151.5 49.145.163.125 49.145.169.78
49.145.101.29 49.145.194.240 49.145.2.164 49.145.212.15
49.145.169.59 49.145.216.127 49.145.34.14 49.145.241.36
49.145.254.227 49.145.37.168 49.145.37.120 49.145.73.145