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

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

;; QUESTION SECTION:
;39.42.82.105.			IN	A

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

;; Query time: 94 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 07 17:22:35 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 105.82.42.39.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 105.82.42.39.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
106.12.186.91 attack
Jan 28 22:50:44 Ubuntu-1404-trusty-64-minimal sshd\[21085\]: Invalid user ipsita from 106.12.186.91
Jan 28 22:50:44 Ubuntu-1404-trusty-64-minimal sshd\[21085\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.186.91
Jan 28 22:50:46 Ubuntu-1404-trusty-64-minimal sshd\[21085\]: Failed password for invalid user ipsita from 106.12.186.91 port 47834 ssh2
Jan 29 00:13:45 Ubuntu-1404-trusty-64-minimal sshd\[25711\]: Invalid user vadabasuta from 106.12.186.91
Jan 29 00:13:45 Ubuntu-1404-trusty-64-minimal sshd\[25711\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.186.91
2020-01-29 07:42:20
1.52.156.182 attackspambots
Unauthorized connection attempt detected from IP address 1.52.156.182 to port 23 [J]
2020-01-29 08:05:37
113.137.36.187 attackspam
Unauthorized connection attempt detected from IP address 113.137.36.187 to port 2220 [J]
2020-01-29 07:59:33
200.53.20.106 attackbotsspam
Unauthorized connection attempt detected from IP address 200.53.20.106 to port 8080 [J]
2020-01-29 07:51:06
46.32.60.139 attackbots
Unauthorized connection attempt detected from IP address 46.32.60.139 to port 2220 [J]
2020-01-29 08:03:05
156.67.107.13 attackspam
Unauthorized connection attempt detected from IP address 156.67.107.13 to port 8080 [J]
2020-01-29 08:13:37
189.17.145.132 attackspambots
Unauthorized connection attempt detected from IP address 189.17.145.132 to port 1433 [J]
2020-01-29 07:53:06
89.120.217.41 attackspam
Unauthorized connection attempt detected from IP address 89.120.217.41 to port 4567 [J]
2020-01-29 08:00:20
95.165.19.198 attackspambots
Unauthorized connection attempt detected from IP address 95.165.19.198 to port 81 [J]
2020-01-29 07:59:55
14.34.165.243 attackbots
Unauthorized connection attempt detected from IP address 14.34.165.243 to port 23 [J]
2020-01-29 07:47:15
79.133.137.18 attackbotsspam
Unauthorized connection attempt detected from IP address 79.133.137.18 to port 2323 [J]
2020-01-29 07:45:59
124.235.138.161 attackspam
Unauthorized connection attempt detected from IP address 124.235.138.161 to port 8080 [J]
2020-01-29 07:36:53
145.239.91.88 attackbotsspam
Unauthorized connection attempt detected from IP address 145.239.91.88 to port 2220 [J]
2020-01-29 07:57:16
125.76.235.86 attack
Unauthorized connection attempt detected from IP address 125.76.235.86 to port 1433 [J]
2020-01-29 07:36:25
180.76.150.17 attack
Invalid user exam from 180.76.150.17 port 56564
2020-01-29 07:54:25

Recently Reported IPs

112.47.132.148 45.66.177.48 36.85.150.148 223.149.180.92
145.239.24.178 124.121.27.97 179.107.52.223 120.229.94.9
110.77.239.153 60.223.254.67 36.134.85.73 115.59.20.212
113.110.216.45 181.44.232.218 116.21.14.131 213.92.254.214
177.8.153.205 125.164.20.197 114.119.137.85 114.119.135.37