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

;; QUESTION SECTION:
;45.83.64.3.			IN	A

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

;; Query time: 65 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Sep 16 05:56:48 CST 2022
;; MSG SIZE  rcvd: 103
Host info
Host 3.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 3.64.83.45.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
144.217.164.104 attackbotsspam
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.217.164.104  user=root
Failed password for root from 144.217.164.104 port 60290 ssh2
Failed password for root from 144.217.164.104 port 60290 ssh2
Failed password for root from 144.217.164.104 port 60290 ssh2
Failed password for root from 144.217.164.104 port 60290 ssh2
2019-06-22 22:11:21
89.210.85.54 attackbots
Telnet Server BruteForce Attack
2019-06-22 21:52:37
92.50.32.99 attackspambots
proto=tcp  .  spt=59296  .  dpt=25  .     (listed on Blocklist de  Jun 21)     (167)
2019-06-22 22:10:01
120.52.152.17 attack
22.06.2019 13:17:47 Connection to port 18081 blocked by firewall
2019-06-22 21:45:29
37.208.66.215 attackspambots
[portscan] Port scan
2019-06-22 21:34:15
213.32.69.98 attack
Invalid user server from 213.32.69.98 port 53370
2019-06-22 21:40:58
200.6.173.58 attackbots
Sending SPAM email
2019-06-22 22:19:28
89.234.157.254 attackbots
Multiple SSH auth failures recorded by fail2ban
2019-06-22 21:49:12
169.239.44.14 attackbotsspam
proto=tcp  .  spt=47862  .  dpt=25  .     (listed on Blocklist de  Jun 21)     (160)
2019-06-22 22:20:49
138.68.29.52 attack
Jun 22 06:09:51 mail sshd\[18997\]: Invalid user presta from 138.68.29.52 port 60280
Jun 22 06:09:51 mail sshd\[18997\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.29.52
Jun 22 06:09:53 mail sshd\[18997\]: Failed password for invalid user presta from 138.68.29.52 port 60280 ssh2
Jun 22 06:11:09 mail sshd\[19169\]: Invalid user zhua from 138.68.29.52 port 46282
Jun 22 06:11:09 mail sshd\[19169\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.29.52
2019-06-22 21:44:31
185.220.101.35 attack
Multiple SSH auth failures recorded by fail2ban
2019-06-22 22:34:47
104.196.16.112 attack
Jun 22 13:54:50 work-partkepr sshd\[7345\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.196.16.112  user=root
Jun 22 13:54:52 work-partkepr sshd\[7345\]: Failed password for root from 104.196.16.112 port 36222 ssh2
...
2019-06-22 22:36:35
68.183.84.15 attackbotsspam
Jun 22 06:15:32 ArkNodeAT sshd\[781\]: Invalid user developer from 68.183.84.15
Jun 22 06:15:32 ArkNodeAT sshd\[781\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.84.15
Jun 22 06:15:34 ArkNodeAT sshd\[781\]: Failed password for invalid user developer from 68.183.84.15 port 36200 ssh2
2019-06-22 21:46:13
142.93.139.5 attack
proto=tcp  .  spt=33582  .  dpt=25  .     (listed on Blocklist de  Jun 21)     (164)
2019-06-22 22:15:39
189.199.48.32 attackbots
Invalid user admin from 189.199.48.32 port 22860
2019-06-22 21:37:20

Recently Reported IPs

162.142.125.122 181.174.165.193 176.32.34.172 167.248.133.246
176.121.14.71 176.32.34.134 181.174.164.38 185.61.138.19
185.61.138.43 185.61.138.77 167.94.145.4 185.61.138.91
185.61.138.137 185.61.138.102 185.61.138.231 193.56.28.96
185.11.146.193 91.243.190.154 167.94.145.255 185.61.138.69