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

Region: Utah

Country: United States

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

;; QUESTION SECTION:
;130.57.8.68.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 01 09:53:35 CST 2025
;; MSG SIZE  rcvd: 104
Host info
Host 68.8.57.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 68.8.57.130.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
103.84.93.32 attackspam
Apr  4 00:37:24 nextcloud sshd\[15818\]: Invalid user teamspeak from 103.84.93.32
Apr  4 00:37:24 nextcloud sshd\[15818\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.84.93.32
Apr  4 00:37:26 nextcloud sshd\[15818\]: Failed password for invalid user teamspeak from 103.84.93.32 port 42356 ssh2
2020-04-04 07:06:20
106.12.26.101 attackspam
SSH bruteforce (Triggered fail2ban)
2020-04-04 07:03:43
58.221.7.174 attackbots
Invalid user tkl from 58.221.7.174 port 36026
2020-04-04 07:12:18
103.28.33.77 attack
Apr  3 23:40:43 tuxlinux sshd[50558]: Invalid user mhuang from 103.28.33.77 port 38224
Apr  3 23:40:43 tuxlinux sshd[50558]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.28.33.77 
Apr  3 23:40:43 tuxlinux sshd[50558]: Invalid user mhuang from 103.28.33.77 port 38224
Apr  3 23:40:43 tuxlinux sshd[50558]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.28.33.77 
Apr  3 23:40:43 tuxlinux sshd[50558]: Invalid user mhuang from 103.28.33.77 port 38224
Apr  3 23:40:43 tuxlinux sshd[50558]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.28.33.77 
Apr  3 23:40:45 tuxlinux sshd[50558]: Failed password for invalid user mhuang from 103.28.33.77 port 38224 ssh2
...
2020-04-04 07:01:32
167.71.202.162 attackspambots
Invalid user gkv from 167.71.202.162 port 43730
2020-04-04 06:55:27
187.178.18.180 attack
Automatic report - Port Scan Attack
2020-04-04 07:22:31
34.92.57.66 attackbotsspam
Apr  3 23:33:14 minden010 sshd[5008]: Failed password for root from 34.92.57.66 port 13360 ssh2
Apr  3 23:41:02 minden010 sshd[7823]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=34.92.57.66
Apr  3 23:41:05 minden010 sshd[7823]: Failed password for invalid user zhengdelian from 34.92.57.66 port 20512 ssh2
...
2020-04-04 06:47:40
129.226.73.26 attackbots
Apr  4 00:15:40 pve sshd[12827]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.226.73.26 
Apr  4 00:15:41 pve sshd[12827]: Failed password for invalid user ke from 129.226.73.26 port 43404 ssh2
Apr  4 00:21:22 pve sshd[13697]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.226.73.26
2020-04-04 06:53:02
91.133.139.70 attack
1585950021 - 04/03/2020 23:40:21 Host: 91.133.139.70/91.133.139.70 Port: 445 TCP Blocked
2020-04-04 07:24:06
185.188.98.39 attack
Port probing on unauthorized port 23
2020-04-04 07:19:08
148.70.183.250 attackbots
$f2bV_matches
2020-04-04 06:46:20
111.67.206.4 attackbotsspam
Apr  3 23:31:14 ns382633 sshd\[11052\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.67.206.4  user=root
Apr  3 23:31:16 ns382633 sshd\[11052\]: Failed password for root from 111.67.206.4 port 36322 ssh2
Apr  3 23:40:55 ns382633 sshd\[13340\]: Invalid user bx from 111.67.206.4 port 58184
Apr  3 23:40:55 ns382633 sshd\[13340\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.67.206.4
Apr  3 23:40:58 ns382633 sshd\[13340\]: Failed password for invalid user bx from 111.67.206.4 port 58184 ssh2
2020-04-04 06:51:57
101.91.160.243 attackbots
Invalid user www from 101.91.160.243 port 43612
2020-04-04 07:16:49
159.65.35.14 attackbotsspam
B: Abusive ssh attack
2020-04-04 07:11:05
107.174.233.133 attack
Apr  3 23:23:13 reporting2 sshd[12901]: reveeclipse mapping checking getaddrinfo for 107-174-233-133-host.colocrossing.com [107.174.233.133] failed - POSSIBLE BREAK-IN ATTEMPT!
Apr  3 23:23:13 reporting2 sshd[12901]: Invalid user yangxin from 107.174.233.133
Apr  3 23:23:13 reporting2 sshd[12901]: Failed password for invalid user yangxin from 107.174.233.133 port 49620 ssh2
Apr  3 23:36:53 reporting2 sshd[22793]: reveeclipse mapping checking getaddrinfo for 107-174-233-133-host.colocrossing.com [107.174.233.133] failed - POSSIBLE BREAK-IN ATTEMPT!
Apr  3 23:36:53 reporting2 sshd[22793]: User r.r from 107.174.233.133 not allowed because not listed in AllowUsers
Apr  3 23:36:53 reporting2 sshd[22793]: Failed password for invalid user r.r from 107.174.233.133 port 48814 ssh2
Apr  3 23:42:02 reporting2 sshd[26228]: reveeclipse mapping checking getaddrinfo for 107-174-233-133-host.colocrossing.com [107.174.233.133] failed - POSSIBLE BREAK-IN ATTEMPT!
Apr  3 23:42:02 reportin........
-------------------------------
2020-04-04 07:20:03

Recently Reported IPs

79.184.216.133 87.225.14.10 151.31.52.7 29.93.117.110
57.55.234.89 149.55.250.46 65.151.169.45 254.245.106.229
108.107.92.105 121.37.222.5 6.48.57.14 206.151.155.226
126.14.122.238 152.75.198.69 239.101.244.93 226.49.139.46
131.244.56.57 89.151.15.242 137.136.106.0 40.50.59.58