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

Region: Kentucky

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

;; QUESTION SECTION:
;74.136.16.139.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Dec 16 13:19:39 CST 2025
;; MSG SIZE  rcvd: 106
Host info
139.16.136.74.in-addr.arpa domain name pointer syn-074-136-016-139.res.spectrum.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
139.16.136.74.in-addr.arpa	name = syn-074-136-016-139.res.spectrum.com.

Authoritative answers can be found from:

Related IP info:
Related comments:
IP Type Details Datetime
69.167.40.150 attack
Fraud Attack running bots
2020-05-14 03:29:43
203.209.181.58 attackspambots
Unauthorized connection attempt from IP address 203.209.181.58 on Port 445(SMB)
2020-05-14 03:55:03
182.150.22.233 attackbots
Invalid user user from 182.150.22.233 port 54958
2020-05-14 03:32:58
138.128.209.35 attackspam
Found by fail2ban
2020-05-14 03:42:10
89.248.168.244 attack
May 13 21:11:30 debian-2gb-nbg1-2 kernel: \[11655947.227420\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=89.248.168.244 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=13439 PROTO=TCP SPT=40762 DPT=4935 WINDOW=1024 RES=0x00 SYN URGP=0
2020-05-14 03:23:57
49.247.134.133 attack
ssh brute force
2020-05-14 04:01:04
178.40.25.63 attackspam
Brute-Force
2020-05-14 04:01:54
190.194.157.178 attackspam
May 13 01:05:01 srv01 sshd[25979]: reveeclipse mapping checking getaddrinfo for 178-157-194-190.cab.prima.net.ar [190.194.157.178] failed - POSSIBLE BREAK-IN ATTEMPT!
May 13 01:05:01 srv01 sshd[25979]: Invalid user ulus from 190.194.157.178
May 13 01:05:01 srv01 sshd[25979]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.194.157.178 
May 13 01:05:03 srv01 sshd[25979]: Failed password for invalid user ulus from 190.194.157.178 port 54092 ssh2
May 13 01:05:03 srv01 sshd[25979]: Received disconnect from 190.194.157.178: 11: Bye Bye [preauth]
May 13 01:13:12 srv01 sshd[26382]: reveeclipse mapping checking getaddrinfo for 178-157-194-190.cab.prima.net.ar [190.194.157.178] failed - POSSIBLE BREAK-IN ATTEMPT!
May 13 01:13:12 srv01 sshd[26382]: Invalid user oracle from 190.194.157.178
May 13 01:13:12 srv01 sshd[26382]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.194.157.178 
May 13 01:1........
-------------------------------
2020-05-14 03:55:32
222.186.42.137 attackbots
05/13/2020-15:54:25.024192 222.186.42.137 Protocol: 6 ET SCAN Potential SSH Scan
2020-05-14 03:59:30
51.91.156.199 attackbots
SSH Brute-Force reported by Fail2Ban
2020-05-14 03:44:48
62.99.119.151 attackbotsspam
20/5/13@13:21:41: FAIL: IoT-Telnet address from=62.99.119.151
...
2020-05-14 03:36:48
222.186.175.169 attackspambots
May 13 19:34:43 ip-172-31-61-156 sshd[24354]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.169  user=root
May 13 19:34:45 ip-172-31-61-156 sshd[24354]: Failed password for root from 222.186.175.169 port 20076 ssh2
...
2020-05-14 03:36:16
51.89.200.126 attack
Automatic report - XMLRPC Attack
2020-05-14 03:46:29
92.87.96.104 attackbotsspam
Automatic report - Port Scan Attack
2020-05-14 03:35:12
54.36.148.209 attackbotsspam
[Wed May 13 19:32:33.038967 2020] [:error] [pid 23852:tid 140604151064320] [client 54.36.148.209:59656] [client 54.36.148.209] ModSecurity: Access denied with code 403 (phase 2). Matched phrase "AhrefsBot" at REQUEST_HEADERS:User-Agent. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-913-SCANNER-DETECTION.conf"] [line "183"] [id "913102"] [msg "Found User-Agent associated with web crawler/bot"] [data "Matched Data: AhrefsBot found within REQUEST_HEADERS:User-Agent: mozilla/5.0 (compatible; ahrefsbot/6.1; +http://ahrefs.com/robot/)"] [severity "CRITICAL"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-reputation-crawler"] [tag "OWASP_CRS"] [tag "OWASP_CRS/AUTOMATION/CRAWLER"] [tag "WASCTC/WASC-21"] [tag "OWASP_TOP_10/A7"] [tag "PCI/6.5.10"] [tag "paranoia-level/2"] [hostname "karangploso.jatim.bmkg.go.id"] [uri "/index.php/tugas-dan-wilayah-kerja/737-klimatologi/agroklimatologi/kalender-tanam-katam-terpadu/k
...
2020-05-14 03:29:18

Recently Reported IPs

231.91.117.179 195.99.240.238 110.187.181.177 35.144.13.95
29.205.156.100 251.44.106.79 85.75.4.108 175.188.149.214
140.19.108.221 83.166.71.81 95.8.156.175 123.111.32.62
226.78.198.149 210.161.192.60 15.55.52.86 118.17.34.14
197.154.102.111 239.221.249.219 120.185.100.81 170.166.122.206