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

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:
IP Type Details Datetime
45.83.64.255 proxy
45.83.64.255
2023-06-08 13:14:10
45.83.64.235 attackbotsspam
port scan and connect, tcp 80 (http)
2020-09-29 02:48:45
45.83.64.235 attackspambots
port scan and connect, tcp 80 (http)
2020-09-28 18:55:56
45.83.64.178 attackspambots
Port Scan detected!
...
2020-08-30 04:30:20
45.83.64.26 attack
port scan and connect, tcp 143 (imap)
2020-08-23 07:44:39
45.83.64.148 attack
Honeypot hit.
2020-08-17 06:37:32
45.83.64.18 attackbots
Unauthorised access (Aug 11) SRC=45.83.64.18 LEN=40 TOS=0x10 PREC=0x40 TTL=57 ID=1337 DF TCP DPT=21 WINDOW=0 SYN
2020-08-12 03:56:16
45.83.64.174 attack
Unauthorized connection attempt detected from IP address 45.83.64.174 to port 110
2020-07-25 21:58:00
45.83.64.190 attack
Unauthorized connection attempt detected from IP address 45.83.64.190 to port 110
2020-07-25 21:11:17
45.83.64.22 attackbots
Hit honeypot r.
2020-07-18 03:28:54
45.83.64.138 attackbots
Port scan denied
2020-07-13 23:06:08
45.83.64.229 attack
Unauthorized connection attempt detected from IP address 45.83.64.229 to port 102
2020-07-09 07:37:55
45.83.64.177 attack
Unauthorized connection attempt detected from IP address 45.83.64.177 to port 102
2020-07-09 06:09:37
45.83.64.232 attack
Unauthorized connection attempt detected from IP address 45.83.64.232 to port 102
2020-07-09 05:48:12
45.83.64.101 attackspambots
Unauthorized connection attempt detected from IP address 45.83.64.101 to port 102
2020-07-09 05:28:19
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 45.83.64.82
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 61729
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;45.83.64.82.			IN	A

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

;; Query time: 144 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 07 17:15:15 CST 2022
;; MSG SIZE  rcvd: 104
Host info
Host 82.64.83.45.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 82.64.83.45.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
205.185.124.152 attackspam
Mar 30 05:24:36 rama sshd[555641]: Invalid user master from 205.185.124.152
Mar 30 05:24:36 rama sshd[555641]: Failed none for invalid user master from 205.185.124.152 port 56832 ssh2
Mar 30 05:24:37 rama sshd[555641]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=205.185.124.152 
Mar 30 05:24:39 rama sshd[555641]: Failed password for invalid user master from 205.185.124.152 port 56832 ssh2
Mar 30 05:24:41 rama sshd[555641]: Failed password for invalid user master from 205.185.124.152 port 56832 ssh2
Mar 30 05:24:44 rama sshd[555641]: Failed password for invalid user master from 205.185.124.152 port 56832 ssh2
Mar 30 05:24:44 rama sshd[555641]: Connection closed by 205.185.124.152 [preauth]
Mar 30 05:24:44 rama sshd[555641]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=205.185.124.152 
Mar 30 05:24:47 rama sshd[555683]: Invalid user mas from 205.185.124.152
Mar 30 05:24:47 rama sshd[555683]: pam........
-------------------------------
2020-03-30 20:37:16
194.78.179.178 attackspam
Brute force SMTP login attempted.
...
2020-03-30 20:59:44
117.50.124.122 attackspambots
Attempted connection to port 1433.
2020-03-30 21:00:34
138.197.158.118 attackbots
Mar 30 12:00:28 ws26vmsma01 sshd[23937]: Failed password for root from 138.197.158.118 port 34386 ssh2
...
2020-03-30 20:26:54
91.234.194.246 attackspam
91.234.194.246 - - [30/Mar/2020:14:45:49 +0200] "GET /wp-login.php HTTP/1.1" 200 6363 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
91.234.194.246 - - [30/Mar/2020:14:45:51 +0200] "POST /wp-login.php HTTP/1.1" 200 7262 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
91.234.194.246 - - [30/Mar/2020:14:45:51 +0200] "POST /xmlrpc.php HTTP/1.1" 200 427 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2020-03-30 21:04:36
45.6.72.17 attackbots
Mar 30 14:42:56 vpn01 sshd[12681]: Failed password for root from 45.6.72.17 port 54628 ssh2
...
2020-03-30 20:57:53
187.8.159.140 attackspambots
fail2ban
2020-03-30 20:24:08
118.185.9.178 attackspam
03/30/2020-08:45:48.063264 118.185.9.178 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-03-30 21:12:50
220.132.72.94 attackbotsspam
Mar 30 13:25:52 vpn01 sshd[11333]: Failed password for root from 220.132.72.94 port 52514 ssh2
...
2020-03-30 20:33:43
106.51.80.198 attack
Mar 30 12:33:37 sigma sshd\[540\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.51.80.198  user=rootMar 30 12:50:23 sigma sshd\[1971\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.51.80.198  user=root
...
2020-03-30 20:43:21
104.238.116.19 attackspam
$f2bV_matches
2020-03-30 20:25:27
103.129.222.135 attack
$f2bV_matches
2020-03-30 20:27:30
159.65.161.40 attackspam
SSH invalid-user multiple login try
2020-03-30 21:08:31
106.12.211.254 attackbots
SSH Brute-Force reported by Fail2Ban
2020-03-30 20:54:13
71.88.252.88 attackbotsspam
Automatic report - Port Scan Attack
2020-03-30 20:50:19

Recently Reported IPs

185.107.132.51 106.51.130.164 66.150.8.84 111.53.61.70
188.166.221.11 154.201.50.78 196.202.194.152 120.244.206.107
143.198.141.151 172.119.78.166 177.91.133.183 68.183.157.215
113.100.193.174 112.66.111.39 175.107.5.9 42.237.25.76
36.89.51.19 186.236.16.86 178.159.100.68 120.195.199.62