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: IANA Special-Purpose Address

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

;; QUESTION SECTION:
;245.158.0.68.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 01 03:39:58 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 68.0.158.245.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.0.158.245.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
37.112.63.104 attackbotsspam
Unauthorized connection attempt detected from IP address 37.112.63.104 to port 2220 [J]
2020-01-22 03:17:41
134.209.254.186 attackspambots
php WP PHPmyadamin ABUSE blocked for 12h
2020-01-22 03:42:38
45.134.179.15 attack
Jan 21 20:36:24 debian-2gb-nbg1-2 kernel: \[1894667.813886\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=45.134.179.15 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=16926 PROTO=TCP SPT=46599 DPT=5362 WINDOW=1024 RES=0x00 SYN URGP=0
2020-01-22 03:36:37
122.51.133.238 attackspambots
Unauthorized connection attempt detected from IP address 122.51.133.238 to port 2220 [J]
2020-01-22 03:23:15
218.92.0.148 attack
Brute-force attempt banned
2020-01-22 03:15:11
37.130.79.237 attack
01/21/2020-13:56:52.524890 37.130.79.237 Protocol: 6 ET SCAN Suspicious inbound to mySQL port 3306
2020-01-22 03:51:33
149.200.213.2 attackbots
Excessive Port-Scanning
2020-01-22 03:19:37
82.207.246.239 attackbotsspam
Jan 21 15:27:41 tor-proxy-04 sshd\[3426\]: Invalid user pi from 82.207.246.239 port 44272
Jan 21 15:27:41 tor-proxy-04 sshd\[3426\]: Connection closed by 82.207.246.239 port 44272 \[preauth\]
Jan 21 15:27:41 tor-proxy-04 sshd\[3428\]: Invalid user pi from 82.207.246.239 port 44278
Jan 21 15:27:41 tor-proxy-04 sshd\[3428\]: Connection closed by 82.207.246.239 port 44278 \[preauth\]
...
2020-01-22 03:31:07
163.44.150.139 attackspam
Unauthorized connection attempt detected from IP address 163.44.150.139 to port 2220 [J]
2020-01-22 03:23:00
95.24.202.39 attack
Jan 21 13:57:58 mout sshd[1353]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=95.24.202.39
Jan 21 13:57:58 mout sshd[1353]: Invalid user admin from 95.24.202.39 port 41106
Jan 21 13:58:00 mout sshd[1353]: Failed password for invalid user admin from 95.24.202.39 port 41106 ssh2
2020-01-22 03:10:58
198.108.67.48 attack
Honeypot hit: misc
2020-01-22 03:14:46
58.87.66.249 attackbots
Jan 21 12:16:39 onepro2 sshd[2938]: Failed password for invalid user admin from 58.87.66.249 port 33852 ssh2
Jan 21 12:42:45 onepro2 sshd[3358]: Failed password for root from 58.87.66.249 port 41878 ssh2
Jan 21 12:47:01 onepro2 sshd[3508]: Failed password for root from 58.87.66.249 port 38596 ssh2
2020-01-22 03:46:10
159.89.93.122 attack
php WP PHPmyadamin ABUSE blocked for 12h
2020-01-22 03:42:09
181.171.20.168 attackspambots
Invalid user rocky from 181.171.20.168 port 29031
2020-01-22 03:33:23
45.65.197.56 attackspam
Unauthorized connection attempt detected from IP address 45.65.197.56 to port 23 [J]
2020-01-22 03:13:59

Recently Reported IPs

212.26.17.191 26.178.56.80 199.197.73.54 255.252.39.19
218.11.171.53 83.159.141.53 34.2.49.58 125.45.137.151
82.114.139.253 163.70.64.174 82.167.147.19 189.253.222.203
174.220.165.247 215.33.133.200 17.162.121.180 199.20.180.253
106.55.150.182 56.241.62.71 6.101.186.119 237.110.211.80