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

Region: Washington

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

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

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

;; Query time: 103 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jul 02 16:50:41 CST 2020
;; MSG SIZE  rcvd: 116
Host info
Host 138.34.3.166.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server:		183.60.82.98
Address:	183.60.82.98#53

** server can't find 138.34.3.166.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
177.66.228.7 attackspambots
SMTP-sasl brute force
...
2019-06-24 22:56:37
193.33.8.98 attack
Unauthorized access to SSH at 24/Jun/2019:12:07:33 +0000.
2019-06-24 22:37:37
185.254.122.35 attackbots
Jun 24 12:06:03   TCP Attack: SRC=185.254.122.35 DST=[Masked] LEN=40 TOS=0x00 PREC=0x00 TTL=246  PROTO=TCP SPT=57369 DPT=25900 WINDOW=1024 RES=0x00 SYN URGP=0
2019-06-24 22:48:00
87.126.213.254 attack
Our company is getting attacks from this Bulgarian IP...someone from that IP is trying to connect to my mikrotik router...with winbox/the dude app.
Please consider blocking this IP in your firewall.
2019-06-24 22:20:59
91.121.171.149 attackbots
Blocked user enumeration attempt
2019-06-24 22:50:53
111.94.116.31 attack
Brute forcing Wordpress login
2019-06-24 23:05:01
52.169.140.40 attackspam
2019-06-24T13:59:54.202039abusebot-4.cloudsearch.cf sshd\[6411\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.169.140.40  user=ftp
2019-06-24 22:23:33
52.227.166.139 attackbots
2019-06-24T13:33:01.733709hub.schaetter.us sshd\[22141\]: Invalid user git from 52.227.166.139
2019-06-24T13:33:01.788204hub.schaetter.us sshd\[22141\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.227.166.139
2019-06-24T13:33:03.444695hub.schaetter.us sshd\[22141\]: Failed password for invalid user git from 52.227.166.139 port 54378 ssh2
2019-06-24T13:36:29.108154hub.schaetter.us sshd\[22151\]: Invalid user worker from 52.227.166.139
2019-06-24T13:36:29.151958hub.schaetter.us sshd\[22151\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.227.166.139
...
2019-06-24 22:20:15
54.240.3.30 attack
From: CryptoLover 
2019-06-24 23:10:09
142.4.214.159 attackspambots
ENG,WP GET /wp-login.php
2019-06-24 22:48:35
191.53.222.178 attackbotsspam
Jun 24 08:08:21 web1 postfix/smtpd[26703]: warning: unknown[191.53.222.178]: SASL PLAIN authentication failed: authentication failure
...
2019-06-24 22:15:45
91.203.73.180 attackspam
wp brute-force
2019-06-24 22:12:03
36.68.128.182 attackspam
Unauthorised access (Jun 24) SRC=36.68.128.182 LEN=52 TTL=114 ID=7987 DF TCP DPT=445 WINDOW=8192 SYN
2019-06-24 23:02:30
218.92.0.148 attackspambots
tried it too often
2019-06-24 22:22:58
37.187.115.201 attackspambots
20 attempts against mh-ssh on mist.magehost.pro
2019-06-24 22:04:36

Recently Reported IPs

92.143.71.94 161.203.162.239 198.211.49.155 2.155.152.226
118.31.115.42 15.57.117.57 194.103.170.109 139.129.233.107
212.66.239.88 222.65.180.170 111.190.181.37 198.178.107.60
94.153.192.77 57.184.142.104 84.197.162.211 187.34.138.36
148.38.220.255 222.4.70.8 173.15.180.203 183.45.221.5