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

Internet Service Provider: Invitech Megoldasok ZRT.

Hostname: unknown

Organization: unknown

Usage Type: Fixed Line ISP

Comments:
Type Details Datetime
attackbotsspam
Aug 12 01:18:59 rigel postfix/smtpd[9173]: warning: hostname keve-82-197.pool.kevenet.hu does not resolve to address 91.82.42.197: Name or service not known
Aug 12 01:18:59 rigel postfix/smtpd[9173]: connect from unknown[91.82.42.197]
Aug 12 01:19:00 rigel postfix/smtpd[9173]: warning: unknown[91.82.42.197]: SASL CRAM-MD5 authentication failed: authentication failure
Aug 12 01:19:00 rigel postfix/smtpd[9173]: warning: unknown[91.82.42.197]: SASL PLAIN authentication failed: authentication failure
Aug 12 01:19:00 rigel postfix/smtpd[9173]: warning: unknown[91.82.42.197]: SASL LOGIN authentication failed: authentication failure
Aug 12 01:19:00 rigel postfix/smtpd[9173]: disconnect from unknown[91.82.42.197]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=91.82.42.197
2019-08-12 19:39:23
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 91.82.42.197
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 38987
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 3 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Mon Aug 12 19:39:16 CST 2019
;; MSG SIZE  rcvd: 116
Host info
197.42.82.91.in-addr.arpa domain name pointer keve-82-197.pool.kevenet.hu.
Nslookup info:
Server:		67.207.67.2
Address:	67.207.67.2#53

Non-authoritative answer:
197.42.82.91.in-addr.arpa	name = keve-82-197.pool.kevenet.hu.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
212.50.15.18 attackbotsspam
Absender hat Spam-Falle ausgel?st
2019-11-05 20:10:29
212.92.106.146 attack
RDP brute force attack detected by fail2ban
2019-11-05 19:45:20
113.14.132.165 attackspam
port scan and connect, tcp 23 (telnet)
2019-11-05 19:46:03
106.75.17.245 attackbotsspam
Invalid user ops123 from 106.75.17.245 port 60422
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.17.245
Failed password for invalid user ops123 from 106.75.17.245 port 60422 ssh2
Invalid user zxcasdqwe from 106.75.17.245 port 36280
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.17.245
2019-11-05 19:45:48
182.61.133.10 attackbotsspam
Nov  4 20:05:35 saengerschafter sshd[374]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.133.10  user=r.r
Nov  4 20:05:37 saengerschafter sshd[374]: Failed password for r.r from 182.61.133.10 port 37538 ssh2
Nov  4 20:05:37 saengerschafter sshd[374]: Received disconnect from 182.61.133.10: 11: Bye Bye [preauth]
Nov  4 20:17:07 saengerschafter sshd[1366]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.133.10  user=r.r
Nov  4 20:17:09 saengerschafter sshd[1366]: Failed password for r.r from 182.61.133.10 port 45180 ssh2
Nov  4 20:17:09 saengerschafter sshd[1366]: Received disconnect from 182.61.133.10: 11: Bye Bye [preauth]
Nov  4 20:21:49 saengerschafter sshd[1800]: Invalid user csgoserver from 182.61.133.10
Nov  4 20:21:49 saengerschafter sshd[1800]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.133.10 
Nov  4 20:21:52 saenger........
-------------------------------
2019-11-05 20:05:10
88.247.108.98 attack
Honeypot attack, port: 23, PTR: 88.247.108.98.static.ttnet.com.tr.
2019-11-05 19:39:40
197.255.176.29 attackbots
Absender hat Spam-Falle ausgel?st
2019-11-05 20:13:12
141.98.81.111 attack
2019-11-04 UTC: 2x - admin(2x)
2019-11-05 20:01:26
148.70.62.12 attack
Nov  5 09:31:14 sd-53420 sshd\[32647\]: Invalid user Sparky1 from 148.70.62.12
Nov  5 09:31:14 sd-53420 sshd\[32647\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.62.12
Nov  5 09:31:16 sd-53420 sshd\[32647\]: Failed password for invalid user Sparky1 from 148.70.62.12 port 39610 ssh2
Nov  5 09:36:54 sd-53420 sshd\[569\]: Invalid user datacenter from 148.70.62.12
Nov  5 09:36:54 sd-53420 sshd\[569\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.62.12
...
2019-11-05 19:52:57
222.186.175.148 attack
Triggered by Fail2Ban at Vostok web server
2019-11-05 19:42:35
167.99.158.136 attackbots
Apr  9 20:16:08 vtv3 sshd\[30642\]: Invalid user annuaire from 167.99.158.136 port 33790
Apr  9 20:16:08 vtv3 sshd\[30642\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.158.136
Apr  9 20:16:10 vtv3 sshd\[30642\]: Failed password for invalid user annuaire from 167.99.158.136 port 33790 ssh2
Apr  9 20:22:03 vtv3 sshd\[455\]: Invalid user now from 167.99.158.136 port 41100
Apr  9 20:22:03 vtv3 sshd\[455\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.158.136
Apr 20 01:56:36 vtv3 sshd\[12596\]: Invalid user mis from 167.99.158.136 port 52252
Apr 20 01:56:36 vtv3 sshd\[12596\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.158.136
Apr 20 01:56:38 vtv3 sshd\[12596\]: Failed password for invalid user mis from 167.99.158.136 port 52252 ssh2
Apr 20 02:01:32 vtv3 sshd\[14989\]: Invalid user demo from 167.99.158.136 port 46214
Apr 20 02:01:32 vtv3 sshd\[14989\]: p
2019-11-05 19:55:23
195.29.155.98 attack
Absender hat Spam-Falle ausgel?st
2019-11-05 20:14:34
115.203.59.33 attack
Honeypot attack, port: 23, PTR: PTR record not found
2019-11-05 20:06:39
200.71.237.244 attackbots
Absender hat Spam-Falle ausgel?st
2019-11-05 20:12:10
1.169.139.94 attack
Port Scan: TCP/23
2019-11-05 19:37:56

Recently Reported IPs

40.77.167.73 46.105.59.149 3.91.184.246 209.85.208.48
49.69.37.6 45.95.147.70 180.148.5.178 79.16.103.135
103.83.105.243 103.23.35.77 134.73.76.196 187.206.127.194
86.109.58.115 5.53.124.85 43.246.245.163 5.54.197.40
195.136.93.56 46.107.146.125 220.132.111.81 217.112.128.64