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

;; QUESTION SECTION:
;45.83.64.194.			IN	A

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

;; Query time: 73 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 08 01:04:02 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 194.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 194.64.83.45.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
208.91.109.18 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2020-04-21 17:20:36
35.190.151.173 attack
Tried to login to my NAS device 272 times
2020-04-21 17:55:29
45.238.229.241 attack
Apr 21 06:17:14 vmd17057 sshd[3966]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.238.229.241 
Apr 21 06:17:16 vmd17057 sshd[3966]: Failed password for invalid user admin from 45.238.229.241 port 64194 ssh2
...
2020-04-21 17:31:12
128.199.72.96 attackbots
2020-04-21T07:52:42.604344abusebot-5.cloudsearch.cf sshd[30008]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.72.96  user=root
2020-04-21T07:52:44.743430abusebot-5.cloudsearch.cf sshd[30008]: Failed password for root from 128.199.72.96 port 43428 ssh2
2020-04-21T07:57:09.187955abusebot-5.cloudsearch.cf sshd[30071]: Invalid user ol from 128.199.72.96 port 56290
2020-04-21T07:57:09.194140abusebot-5.cloudsearch.cf sshd[30071]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.72.96
2020-04-21T07:57:09.187955abusebot-5.cloudsearch.cf sshd[30071]: Invalid user ol from 128.199.72.96 port 56290
2020-04-21T07:57:11.318423abusebot-5.cloudsearch.cf sshd[30071]: Failed password for invalid user ol from 128.199.72.96 port 56290 ssh2
2020-04-21T08:01:35.750723abusebot-5.cloudsearch.cf sshd[30354]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.72.96  user
...
2020-04-21 17:19:39
192.241.239.139 attackbots
srv02 Mass scanning activity detected Target: 1434(ms-sql-m) ..
2020-04-21 17:30:15
49.82.193.166 attackbotsspam
Email rejected due to spam filtering
2020-04-21 17:52:31
94.183.148.77 attackbotsspam
DATE:2020-04-21 05:51:16, IP:94.183.148.77, PORT:telnet Telnet brute force auth on honeypot server (epe-honey1-hq)
2020-04-21 17:17:37
188.16.147.225 attackbots
Port probing on unauthorized port 23
2020-04-21 17:36:08
144.76.38.10 attackbotsspam
20 attempts against mh-misbehave-ban on pole
2020-04-21 17:21:31
106.13.35.176 attackbotsspam
sshd jail - ssh hack attempt
2020-04-21 17:37:27
212.129.154.148 attack
Apr 21 10:12:23 dev0-dcde-rnet sshd[28388]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.129.154.148
Apr 21 10:12:26 dev0-dcde-rnet sshd[28388]: Failed password for invalid user ftpuser from 212.129.154.148 port 49780 ssh2
Apr 21 10:27:42 dev0-dcde-rnet sshd[28514]: Failed password for root from 212.129.154.148 port 40416 ssh2
2020-04-21 17:44:56
223.194.33.72 attackbotsspam
(sshd) Failed SSH login from 223.194.33.72 (-): 2 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr 21 11:21:14 ubnt-55d23 sshd[21755]: Invalid user ii from 223.194.33.72 port 36064
Apr 21 11:21:16 ubnt-55d23 sshd[21755]: Failed password for invalid user ii from 223.194.33.72 port 36064 ssh2
2020-04-21 17:24:59
122.51.125.71 attackbots
Invalid user mv from 122.51.125.71 port 54606
2020-04-21 17:29:19
144.76.176.171 attack
20 attempts against mh-misbehave-ban on milky
2020-04-21 17:26:02
223.206.219.169 attack
trying to access non-authorized port
2020-04-21 17:38:56

Recently Reported IPs

187.162.24.185 128.199.108.153 24.122.195.77 223.99.193.245
14.162.23.53 171.233.199.92 83.149.21.174 191.101.17.113
144.126.157.16 76.8.60.242 61.53.123.219 103.113.208.46
182.121.87.76 182.56.170.17 187.163.135.61 201.150.186.251
185.165.151.1 211.21.102.11 31.210.209.103 36.81.24.208