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

Internet Service Provider: Tentorium Welnes LLC

Hostname: unknown

Organization: unknown

Usage Type: Data Center/Web Hosting/Transit

Comments:
Type Details Datetime
attackbotsspam
Sep 15 03:42:48 our-server-hostname sshd[30783]: Address 192.145.99.71 maps to aofy.ru, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Sep 15 03:42:48 our-server-hostname sshd[30783]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.145.99.71  user=r.r
Sep 15 03:42:50 our-server-hostname sshd[30783]: Failed password for r.r from 192.145.99.71 port 60175 ssh2
Sep 15 03:59:06 our-server-hostname sshd[32531]: Address 192.145.99.71 maps to aofy.ru, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Sep 15 03:59:06 our-server-hostname sshd[32531]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.145.99.71  user=r.r
Sep 15 03:59:08 our-server-hostname sshd[32531]: Failed password for r.r from 192.145.99.71 port 40733 ssh2
Sep 15 04:03:54 our-server-hostname sshd[547]: Address 192.145.99.71 maps to aofy.ru, but this does not map back to the address ........
-------------------------------
2020-09-16 12:00:39
attackspam
Sep 15 03:42:48 our-server-hostname sshd[30783]: Address 192.145.99.71 maps to aofy.ru, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Sep 15 03:42:48 our-server-hostname sshd[30783]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.145.99.71  user=r.r
Sep 15 03:42:50 our-server-hostname sshd[30783]: Failed password for r.r from 192.145.99.71 port 60175 ssh2
Sep 15 03:59:06 our-server-hostname sshd[32531]: Address 192.145.99.71 maps to aofy.ru, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Sep 15 03:59:06 our-server-hostname sshd[32531]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.145.99.71  user=r.r
Sep 15 03:59:08 our-server-hostname sshd[32531]: Failed password for r.r from 192.145.99.71 port 40733 ssh2
Sep 15 04:03:54 our-server-hostname sshd[547]: Address 192.145.99.71 maps to aofy.ru, but this does not map back to the address ........
-------------------------------
2020-09-16 03:49:22
attackspam
Sep 15 03:42:48 our-server-hostname sshd[30783]: Address 192.145.99.71 maps to aofy.ru, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Sep 15 03:42:48 our-server-hostname sshd[30783]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.145.99.71  user=r.r
Sep 15 03:42:50 our-server-hostname sshd[30783]: Failed password for r.r from 192.145.99.71 port 60175 ssh2
Sep 15 03:59:06 our-server-hostname sshd[32531]: Address 192.145.99.71 maps to aofy.ru, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Sep 15 03:59:06 our-server-hostname sshd[32531]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.145.99.71  user=r.r
Sep 15 03:59:08 our-server-hostname sshd[32531]: Failed password for r.r from 192.145.99.71 port 40733 ssh2
Sep 15 04:03:54 our-server-hostname sshd[547]: Address 192.145.99.71 maps to aofy.ru, but this does not map back to the address ........
-------------------------------
2020-09-16 00:19:00
attackbots
Sep 15 03:42:48 our-server-hostname sshd[30783]: Address 192.145.99.71 maps to aofy.ru, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Sep 15 03:42:48 our-server-hostname sshd[30783]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.145.99.71  user=r.r
Sep 15 03:42:50 our-server-hostname sshd[30783]: Failed password for r.r from 192.145.99.71 port 60175 ssh2
Sep 15 03:59:06 our-server-hostname sshd[32531]: Address 192.145.99.71 maps to aofy.ru, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Sep 15 03:59:06 our-server-hostname sshd[32531]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.145.99.71  user=r.r
Sep 15 03:59:08 our-server-hostname sshd[32531]: Failed password for r.r from 192.145.99.71 port 40733 ssh2
Sep 15 04:03:54 our-server-hostname sshd[547]: Address 192.145.99.71 maps to aofy.ru, but this does not map back to the address ........
-------------------------------
2020-09-15 16:12:26
attack
Sep 15 03:42:48 our-server-hostname sshd[30783]: Address 192.145.99.71 maps to aofy.ru, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Sep 15 03:42:48 our-server-hostname sshd[30783]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.145.99.71  user=r.r
Sep 15 03:42:50 our-server-hostname sshd[30783]: Failed password for r.r from 192.145.99.71 port 60175 ssh2
Sep 15 03:59:06 our-server-hostname sshd[32531]: Address 192.145.99.71 maps to aofy.ru, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Sep 15 03:59:06 our-server-hostname sshd[32531]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.145.99.71  user=r.r
Sep 15 03:59:08 our-server-hostname sshd[32531]: Failed password for r.r from 192.145.99.71 port 40733 ssh2
Sep 15 04:03:54 our-server-hostname sshd[547]: Address 192.145.99.71 maps to aofy.ru, but this does not map back to the address ........
-------------------------------
2020-09-15 08:17:40
Comments on same subnet:
IP Type Details Datetime
192.145.99.250 attackbots
Attempted WordPress login: "GET /wp-login.php"
2019-07-14 19:31:30
192.145.99.250 attack
WordPress brute force
2019-07-12 19:51:23
192.145.99.250 attack
Automatic report generated by Wazuh
2019-07-09 05:20:51
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 192.145.99.71
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 24428
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;192.145.99.71.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Sep 15 08:17:36 CST 2020
;; MSG SIZE  rcvd: 117
Host info
71.99.145.192.in-addr.arpa domain name pointer aofy.ru.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
71.99.145.192.in-addr.arpa	name = aofy.ru.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
165.227.147.139 attackspam
port scan and connect, tcp 80 (http)
2019-12-11 06:37:41
193.32.161.113 attack
12/10/2019-16:38:29.402032 193.32.161.113 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2019-12-11 06:28:59
185.156.73.45 attackspambots
Dec 10 23:52:42 debian-2gb-vpn-nbg1-1 kernel: [389546.252918] [UFW BLOCK] IN=eth0 OUT= MAC=96:00:00:38:96:44:d2:74:7f:6e:37:e3:08:00 SRC=185.156.73.45 DST=78.46.192.101 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=60688 PROTO=TCP SPT=40505 DPT=37644 WINDOW=1024 RES=0x00 SYN URGP=0
2019-12-11 06:08:55
71.6.232.6 attackbotsspam
Fail2Ban Ban Triggered
2019-12-11 06:21:46
185.143.223.159 attack
12/10/2019-17:03:16.942550 185.143.223.159 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-12-11 06:11:02
89.248.160.193 attackspambots
Dec 11 01:01:41 debian-2gb-vpn-nbg1-1 kernel: [393685.844651] [UFW BLOCK] IN=eth0 OUT= MAC=96:00:00:38:96:44:d2:74:7f:6e:37:e3:08:00 SRC=89.248.160.193 DST=78.46.192.101 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=38130 PROTO=TCP SPT=58729 DPT=9000 WINDOW=1024 RES=0x00 SYN URGP=0
2019-12-11 06:18:44
176.61.155.104 attackspambots
Dec 10 21:16:02 debian-2gb-vpn-nbg1-1 kernel: [380147.203991] [UFW BLOCK] IN=eth0 OUT= MAC=96:00:00:38:96:44:d2:74:7f:6e:37:e3:08:00 SRC=176.61.155.104 DST=78.46.192.101 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=31337 DF PROTO=TCP SPT=42687 DPT=25500 WINDOW=512 RES=0x00 SYN URGP=0
2019-12-11 06:37:22
185.222.211.165 attackspambots
12/10/2019-23:00:21.694858 185.222.211.165 Protocol: 6 ET DROP Spamhaus DROP Listed Traffic Inbound group 20
2019-12-11 06:29:44
185.176.27.18 attack
firewall-block, port(s): 1905/tcp, 1924/tcp, 1925/tcp, 1930/tcp, 1935/tcp, 1941/tcp
2019-12-11 06:07:05
185.53.88.78 attackbots
firewall-block, port(s): 5060/udp
2019-12-11 06:36:35
185.209.0.51 attack
12/10/2019-16:56:00.262946 185.209.0.51 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2019-12-11 06:04:33
85.209.88.47 attackspambots
ET SCAN Suspicious inbound to mySQL port 3306 - port: 3306 proto: TCP cat: Potentially Bad Traffic
2019-12-11 06:19:46
185.176.27.46 attackspambots
12/10/2019-17:12:06.351046 185.176.27.46 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2019-12-11 06:32:47
210.186.12.113 attackspam
ET SCAN MS Terminal Server Traffic on Non-standard Port - port: 1000 proto: TCP cat: Attempted Information Leak
2019-12-11 06:27:54
162.125.36.1 attackbots
ET POLICY Dropbox.com Offsite File Backup in Use - port: 28530 proto: TCP cat: Potential Corporate Privacy Violation
2019-12-11 06:12:07

Recently Reported IPs

220.81.34.227 56.95.30.49 51.83.69.142 218.250.87.65
161.212.172.104 250.135.153.156 7.77.103.176 3.30.212.213
239.255.255.40 108.210.53.219 244.141.99.45 156.239.240.126
175.97.236.95 206.211.61.160 144.40.146.221 156.54.170.118
124.250.119.209 86.25.191.126 161.230.211.221 216.166.150.86