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

;; QUESTION SECTION:
;1.138.169.104.			IN	A

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

;; Query time: 74 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Sep 26 05:33:46 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 104.169.138.1.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 104.169.138.1.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
187.5.184.178 attack
Unauthorized connection attempt detected from IP address 187.5.184.178 to port 8000 [J]
2020-01-18 16:03:44
182.61.1.49 attack
Jan 18 09:01:36 ncomp sshd[3622]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.1.49  user=root
Jan 18 09:01:38 ncomp sshd[3622]: Failed password for root from 182.61.1.49 port 43412 ssh2
Jan 18 09:04:42 ncomp sshd[3659]: Invalid user echo from 182.61.1.49
2020-01-18 16:05:12
201.116.194.210 attack
Jan 18 08:43:17 dedicated sshd[25148]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.116.194.210  user=root
Jan 18 08:43:19 dedicated sshd[25148]: Failed password for root from 201.116.194.210 port 33572 ssh2
2020-01-18 15:59:15
83.17.166.241 attackbots
Automatic report - SSH Brute-Force Attack
2020-01-18 15:49:36
49.87.75.181 attackspam
Unauthorized connection attempt detected from IP address 49.87.75.181 to port 23 [J]
2020-01-18 15:55:01
187.153.113.98 attackbots
Unauthorized connection attempt detected from IP address 187.153.113.98 to port 4567 [J]
2020-01-18 16:03:12
2.84.157.74 attack
Unauthorized connection attempt detected from IP address 2.84.157.74 to port 80 [J]
2020-01-18 15:57:29
222.186.31.135 attack
Unauthorized connection attempt detected from IP address 222.186.31.135 to port 22 [J]
2020-01-18 15:57:59
196.202.56.86 attackspam
Unauthorized connection attempt detected from IP address 196.202.56.86 to port 4567 [J]
2020-01-18 16:00:11
197.232.241.172 attackspambots
Unauthorized connection attempt detected from IP address 197.232.241.172 to port 8080 [J]
2020-01-18 15:59:39
120.132.116.86 attackspambots
Unauthorized connection attempt detected from IP address 120.132.116.86 to port 2220 [J]
2020-01-18 15:43:11
162.202.36.249 attackspambots
Unauthorized connection attempt detected from IP address 162.202.36.249 to port 23 [J]
2020-01-18 16:06:40
220.180.150.249 attack
Unauthorized connection attempt detected from IP address 220.180.150.249 to port 1433 [J]
2020-01-18 15:58:18
123.206.47.228 attack
Unauthorized connection attempt detected from IP address 123.206.47.228 to port 2220 [J]
2020-01-18 15:42:24
187.178.2.149 attackbots
Unauthorized connection attempt detected from IP address 187.178.2.149 to port 81 [J]
2020-01-18 15:39:31

Recently Reported IPs

1.136.230.70 1.134.81.196 1.140.49.34 1.137.20.179
1.14.138.81 1.135.182.38 1.134.92.229 1.139.243.217
1.138.22.237 1.136.178.123 1.136.104.142 1.136.111.133
1.138.145.76 1.139.242.73 1.135.217.190 1.134.76.4
1.139.120.46 1.139.125.124 1.136.234.78 1.139.138.68