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

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

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

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

;; Query time: 3 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Wed Jun 26 22:00:10 CST 2019
;; MSG SIZE  rcvd: 118
Host info
Host 245.74.145.148.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
*** Can't find 245.74.145.148.in-addr.arpa.: No answer

Authoritative answers can be found from:

Related IP info:
Related comments:
IP Type Details Datetime
49.206.17.36 attack
Invalid user filter from 49.206.17.36 port 33698
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.206.17.36
Failed password for invalid user filter from 49.206.17.36 port 33698 ssh2
Invalid user huawei from 49.206.17.36 port 60572
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.206.17.36
2019-12-30 03:15:03
94.183.194.69 attack
Unauthorized connection attempt detected from IP address 94.183.194.69 to port 9000
2019-12-30 02:44:35
108.84.16.222 attack
Unauthorized connection attempt detected from IP address 108.84.16.222 to port 23
2019-12-30 02:42:21
189.208.208.238 attackspambots
Unauthorized connection attempt detected from IP address 189.208.208.238 to port 23
2019-12-30 02:59:20
52.181.180.198 attackbotsspam
Unauthorized connection attempt detected from IP address 52.181.180.198 to port 3389
2019-12-30 02:51:18
82.60.200.82 attack
Unauthorized connection attempt detected from IP address 82.60.200.82 to port 9090
2019-12-30 03:10:17
14.55.141.205 attackbotsspam
Unauthorized connection attempt detected from IP address 14.55.141.205 to port 82
2019-12-30 02:54:03
34.222.15.100 attackbots
Unauthorized connection attempt detected from IP address 34.222.15.100 to port 8181
2019-12-30 03:16:16
49.51.12.205 attackspambots
Unauthorized connection attempt detected from IP address 49.51.12.205 to port 7777
2019-12-30 03:15:27
213.254.129.55 attackspambots
Unauthorized connection attempt detected from IP address 213.254.129.55 to port 8080
2019-12-30 03:19:30
108.239.90.235 attackbotsspam
Unauthorized connection attempt detected from IP address 108.239.90.235 to port 23
2019-12-30 02:41:54
92.54.200.134 attackbots
Unauthorized connection attempt detected from IP address 92.54.200.134 to port 80
2019-12-30 03:08:56
34.93.149.128 attackspam
Unauthorized connection attempt detected from IP address 34.93.149.128 to port 3389
2019-12-30 03:16:47
66.42.16.239 attackspam
Unauthorized connection attempt detected from IP address 66.42.16.239 to port 23
2019-12-30 03:11:28
65.50.24.82 attack
Unauthorized connection attempt detected from IP address 65.50.24.82 to port 4567
2019-12-30 02:49:06

Recently Reported IPs

187.1.40.51 168.153.198.161 83.248.228.151 137.116.36.196
36.106.196.244 177.126.226.69 139.99.220.58 14.169.135.139
201.48.61.20 82.226.50.23 49.230.108.177 197.234.221.68
175.149.167.227 117.176.58.80 82.117.245.189 91.24.145.162
136.9.128.181 122.35.100.53 55.14.191.247 12.72.217.77