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

;; QUESTION SECTION:
;34.214.199.82.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 22 10:59:59 CST 2025
;; MSG SIZE  rcvd: 106
Host info
82.199.214.34.in-addr.arpa domain name pointer ec2-34-214-199-82.us-west-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
82.199.214.34.in-addr.arpa	name = ec2-34-214-199-82.us-west-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
118.37.91.137 attackspambots
Honeypot attack, port: 81, PTR: PTR record not found
2020-02-16 05:11:15
188.166.234.227 attackbotsspam
Feb 15 05:41:35 sachi sshd\[20714\]: Invalid user test from 188.166.234.227
Feb 15 05:41:35 sachi sshd\[20714\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.234.227
Feb 15 05:41:37 sachi sshd\[20714\]: Failed password for invalid user test from 188.166.234.227 port 42898 ssh2
Feb 15 05:44:17 sachi sshd\[20961\]: Invalid user MayGion from 188.166.234.227
Feb 15 05:44:17 sachi sshd\[20961\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.234.227
2020-02-16 05:10:43
115.75.253.204 attack
Automatic report - Port Scan Attack
2020-02-16 05:02:38
92.194.56.72 attackspambots
fire
2020-02-16 05:37:21
98.207.32.236 attackspam
fire
2020-02-16 05:24:22
210.74.13.5 attackspambots
Dec 22 17:56:03 ms-srv sshd[6077]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.74.13.5
Dec 22 17:56:05 ms-srv sshd[6077]: Failed password for invalid user testing from 210.74.13.5 port 52380 ssh2
2020-02-16 05:14:54
1.203.80.2 attackspambots
Port probing on unauthorized port 1433
2020-02-16 05:10:12
109.225.99.212 attack
20/2/15@09:44:04: FAIL: Alarm-Telnet address from=109.225.99.212
...
2020-02-16 05:23:09
210.74.14.109 attackbotsspam
Dec 15 22:36:55 ms-srv sshd[12841]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.74.14.109
Dec 15 22:36:57 ms-srv sshd[12841]: Failed password for invalid user fries from 210.74.14.109 port 63657 ssh2
2020-02-16 05:14:15
193.106.240.94 attackspambots
0,39-02/32 [bc01/m47] PostRequest-Spammer scoring: lisboa
2020-02-16 05:12:47
114.79.173.41 attackbots
Portscan detected
2020-02-16 05:24:50
118.37.21.223 attack
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-16 05:41:34
118.37.218.113 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-16 05:31:39
49.88.112.77 attack
Feb 15 18:00:43 firewall sshd[31199]: Failed password for root from 49.88.112.77 port 49854 ssh2
Feb 15 18:00:46 firewall sshd[31199]: Failed password for root from 49.88.112.77 port 49854 ssh2
Feb 15 18:00:49 firewall sshd[31199]: Failed password for root from 49.88.112.77 port 49854 ssh2
...
2020-02-16 05:19:25
118.37.74.140 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-16 05:13:43

Recently Reported IPs

86.116.25.69 163.156.27.3 221.155.138.130 140.245.10.211
66.30.61.104 228.211.211.247 132.157.25.158 144.71.172.140
138.145.141.162 145.200.231.58 51.225.68.244 47.25.186.167
167.184.239.145 164.188.129.218 98.232.138.18 94.150.201.179
70.166.131.134 44.96.39.90 143.221.108.32 193.192.5.227