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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 130.83.201.6
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 23915
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;130.83.201.6.			IN	A

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

;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 11 11:40:50 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 6.201.83.130.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 6.201.83.130.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
222.186.175.202 attack
Apr 11 09:23:26 v22018086721571380 sshd[23953]: error: maximum authentication attempts exceeded for root from 222.186.175.202 port 48138 ssh2 [preauth]
2020-04-11 15:27:50
216.244.66.199 attackbots
20 attempts against mh-misbehave-ban on cedar
2020-04-11 15:34:22
138.197.118.32 attackbotsspam
Apr 11 03:59:34 124388 sshd[22266]: Failed password for invalid user admin from 138.197.118.32 port 48044 ssh2
Apr 11 04:04:24 124388 sshd[22312]: Invalid user lidia from 138.197.118.32 port 57938
Apr 11 04:04:24 124388 sshd[22312]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.118.32
Apr 11 04:04:24 124388 sshd[22312]: Invalid user lidia from 138.197.118.32 port 57938
Apr 11 04:04:25 124388 sshd[22312]: Failed password for invalid user lidia from 138.197.118.32 port 57938 ssh2
2020-04-11 15:40:59
219.75.134.27 attack
Apr 11 08:46:28 nextcloud sshd\[28095\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=219.75.134.27  user=root
Apr 11 08:46:30 nextcloud sshd\[28095\]: Failed password for root from 219.75.134.27 port 57532 ssh2
Apr 11 09:00:28 nextcloud sshd\[14779\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=219.75.134.27  user=root
2020-04-11 15:11:38
37.252.187.140 attackspambots
Apr 11 09:55:32 ift sshd\[46787\]: Invalid user guest from 37.252.187.140Apr 11 09:55:34 ift sshd\[46787\]: Failed password for invalid user guest from 37.252.187.140 port 47846 ssh2Apr 11 09:59:10 ift sshd\[47041\]: Failed password for root from 37.252.187.140 port 57026 ssh2Apr 11 10:02:47 ift sshd\[47669\]: Invalid user marietta from 37.252.187.140Apr 11 10:02:49 ift sshd\[47669\]: Failed password for invalid user marietta from 37.252.187.140 port 37976 ssh2
...
2020-04-11 15:09:40
114.67.69.206 attackspam
SSH invalid-user multiple login attempts
2020-04-11 15:09:25
182.138.120.88 attackbotsspam
$f2bV_matches
2020-04-11 15:29:56
175.24.107.201 attackbotsspam
ssh brute force
2020-04-11 15:24:18
111.229.90.2 attack
Apr 11 09:09:48 haigwepa sshd[15469]: Failed password for root from 111.229.90.2 port 42814 ssh2
...
2020-04-11 15:35:28
49.235.76.154 attackspambots
(sshd) Failed SSH login from 49.235.76.154 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr 11 08:11:13 amsweb01 sshd[1855]: Invalid user ftpuser from 49.235.76.154 port 35526
Apr 11 08:11:16 amsweb01 sshd[1855]: Failed password for invalid user ftpuser from 49.235.76.154 port 35526 ssh2
Apr 11 08:29:46 amsweb01 sshd[3756]: Invalid user sys from 49.235.76.154 port 36006
Apr 11 08:29:49 amsweb01 sshd[3756]: Failed password for invalid user sys from 49.235.76.154 port 36006 ssh2
Apr 11 08:34:51 amsweb01 sshd[4268]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.76.154  user=root
2020-04-11 15:12:22
148.66.135.152 attack
WordPress wp-login brute force :: 148.66.135.152 0.096 BYPASS [11/Apr/2020:05:54:54  0000] [censored_2] "POST /wp-login.php HTTP/1.1" 200 2287 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2020-04-11 15:11:25
196.27.127.61 attackspam
Invalid user test from 196.27.127.61 port 57882
2020-04-11 15:28:49
139.162.65.55 attackspam
Apr 11 05:52:34 debian-2gb-nbg1-2 kernel: \[8836159.320454\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=139.162.65.55 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=54321 PROTO=TCP SPT=44547 DPT=53 WINDOW=65535 RES=0x00 SYN URGP=0
2020-04-11 15:15:50
193.202.45.202 attackspam
193.202.45.202 was recorded 21 times by 9 hosts attempting to connect to the following ports: 5060. Incident counter (4h, 24h, all-time): 21, 21, 31
2020-04-11 15:18:34
157.100.58.254 attackspam
(sshd) Failed SSH login from 157.100.58.254 (EC/Ecuador/Provincia de Pichincha/-/host-157-100-58-254.nedetel.net/[AS264668 NEDETEL S.A.]): 1 in the last 3600 secs
2020-04-11 15:22:17

Recently Reported IPs

217.254.182.217 64.194.177.203 129.70.129.52 88.157.27.121
163.149.5.60 243.142.100.255 76.178.179.99 96.15.126.159
7.142.48.141 103.148.148.74 26.51.247.9 244.20.5.227
176.120.255.251 207.90.95.206 108.112.45.125 49.79.142.252
65.29.255.102 106.203.177.128 91.76.214.92 29.104.211.44