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: United States of America (the)

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

;; QUESTION SECTION:
;138.150.68.146.			IN	A

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

;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 12:15:07 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 146.68.150.138.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
server can't find 138.150.68.146.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
172.105.40.217 attackbotsspam
CloudCIX Reconnaissance Scan Detected, PTR: li1992-217.members.linode.com.
2019-10-31 18:38:22
198.211.110.133 attackbots
Oct 31 01:52:14 TORMINT sshd\[17082\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.211.110.133  user=root
Oct 31 01:52:16 TORMINT sshd\[17082\]: Failed password for root from 198.211.110.133 port 51264 ssh2
Oct 31 01:56:13 TORMINT sshd\[17309\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.211.110.133  user=root
...
2019-10-31 18:53:26
120.28.23.146 attack
23/tcp
[2019-10-31]1pkt
2019-10-31 18:59:40
210.103.97.135 attackbots
detected by Fail2Ban
2019-10-31 18:57:16
192.42.116.15 attackbots
Invalid user 111111 from 192.42.116.15 port 56826
2019-10-31 18:33:38
79.36.88.77 attack
81/tcp
[2019-10-31]1pkt
2019-10-31 18:37:06
185.142.236.34 attack
Connection by 185.142.236.34 on port: 2086 got caught by honeypot at 10/31/2019 8:18:04 AM
2019-10-31 18:27:34
185.246.128.26 attackbotsspam
ET SCAN Potential SSH Scan - port: 22 proto: TCP cat: Attempted Information Leak
2019-10-31 18:46:58
201.208.206.197 attackspam
1433/tcp
[2019-10-31]1pkt
2019-10-31 18:29:09
36.70.75.44 attack
445/tcp
[2019-10-31]1pkt
2019-10-31 18:20:10
103.72.144.23 attackspambots
Oct 31 06:17:55 work-partkepr sshd\[29099\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.72.144.23  user=root
Oct 31 06:17:56 work-partkepr sshd\[29099\]: Failed password for root from 103.72.144.23 port 32840 ssh2
...
2019-10-31 18:43:45
177.190.65.247 attack
From CCTV User Interface Log
...::ffff:177.190.65.247 - - [30/Oct/2019:23:47:40 +0000] "GET / HTTP/1.1" 200 960
...
2019-10-31 18:54:45
91.121.205.83 attackspambots
2019-10-31T06:17:16.258933abusebot-5.cloudsearch.cf sshd\[28602\]: Invalid user Montana@2017 from 91.121.205.83 port 46728
2019-10-31 18:44:33
46.188.53.38 attackbots
[portscan] tcp/3389 [MS RDP]
[scan/connect: 4 time(s)]
in spfbl.net:'listed'
*(RWIN=1024)(10311120)
2019-10-31 18:28:06
14.63.212.215 attack
Invalid user test from 14.63.212.215 port 45554
2019-10-31 18:25:36

Recently Reported IPs

19.199.196.147 189.219.246.173 171.53.37.208 92.150.63.176
141.242.193.144 29.180.101.215 121.49.234.106 63.226.126.78
29.183.175.48 60.103.152.168 224.188.85.26 243.249.154.109
160.45.39.79 98.70.141.127 227.43.154.26 236.67.241.73
152.153.244.62 234.96.17.206 106.91.203.194 219.213.114.64