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

Region: Virginia

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:
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#


NetRange:       34.192.0.0 - 34.255.255.255
CIDR:           34.192.0.0/10
NetName:        AT-88-Z
NetHandle:      NET-34-192-0-0-1
Parent:         NET34 (NET-34-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       
Organization:   Amazon Technologies Inc. (AT-88-Z)
RegDate:        2016-09-12
Updated:        2016-09-12
Ref:            https://rdap.arin.net/registry/ip/34.192.0.0



OrgName:        Amazon Technologies Inc.
OrgId:          AT-88-Z
Address:        410 Terry Ave N.
City:           Seattle
StateProv:      WA
PostalCode:     98109
Country:        US
RegDate:        2011-12-08
Updated:        2026-04-17
Comment:        All abuse reports MUST include:
Comment:        * src IP
Comment:        * dest IP (your IP)
Comment:        * dest port
Comment:        * Accurate date/timestamp and timezone of activity
Comment:        * Intensity/frequency (short log extracts)
Comment:        * Your contact details (phone and email) Without these we will be unable to identify the correct owner of the IP address at that point in time.
Ref:            https://rdap.arin.net/registry/entity/AT-88-Z


OrgRoutingHandle: IPROU3-ARIN
OrgRoutingName:   IP Routing
OrgRoutingPhone:  +1-206-555-0000 
OrgRoutingEmail:  aws-routing-poc@amazon.com
OrgRoutingRef:    https://rdap.arin.net/registry/entity/IPROU3-ARIN

OrgDNSHandle: DNS1131-ARIN
OrgDNSName:   DNS
OrgDNSPhone:  +1-202-555-0000 
OrgDNSEmail:  ipmanagement+dns@amazon.com
OrgDNSRef:    https://rdap.arin.net/registry/entity/DNS1131-ARIN

OrgRoutingHandle: ARMP-ARIN
OrgRoutingName:   AWS RPKI Management POC
OrgRoutingPhone:  +1-206-555-0000 
OrgRoutingEmail:  aws-rpki-routing-poc@amazon.com
OrgRoutingRef:    https://rdap.arin.net/registry/entity/ARMP-ARIN

OrgNOCHandle: AANO1-ARIN
OrgNOCName:   Amazon AWS Network Operations
OrgNOCPhone:  +1-206-555-0000 
OrgNOCEmail:  amzn-noc-contact@amazon.com
OrgNOCRef:    https://rdap.arin.net/registry/entity/AANO1-ARIN

OrgAbuseHandle: AEA8-ARIN
OrgAbuseName:   Amazon EC2 Abuse
OrgAbusePhone:  +1-206-555-0000 
OrgAbuseEmail:  trustandsafety@support.aws.com
OrgAbuseRef:    https://rdap.arin.net/registry/entity/AEA8-ARIN

OrgTechHandle: ANO24-ARIN
OrgTechName:   Amazon EC2 Network Operations
OrgTechPhone:  +1-206-555-0000 
OrgTechEmail:  amzn-noc-contact@amazon.com
OrgTechRef:    https://rdap.arin.net/registry/entity/ANO24-ARIN


#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 34.205.139.189
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 57761
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;34.205.139.189.			IN	A

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

;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Apr 28 05:30:38 CST 2026
;; MSG SIZE  rcvd: 107
Host info
189.139.205.34.in-addr.arpa domain name pointer ec2-34-205-139-189.compute-1.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
189.139.205.34.in-addr.arpa	name = ec2-34-205-139-189.compute-1.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
89.248.172.90 attack
Unauthorized connection attempt detected from IP address 89.248.172.90 to port 9000
2019-12-31 21:55:35
42.112.135.195 attackspambots
Unauthorized connection attempt detected from IP address 42.112.135.195 to port 23
2019-12-31 22:00:29
43.249.204.187 attack
Unauthorized connection attempt detected from IP address 43.249.204.187 to port 1433
2019-12-31 22:00:08
58.56.131.246 attackbotsspam
Unauthorized connection attempt detected from IP address 58.56.131.246 to port 445
2019-12-31 22:33:16
183.80.122.207 attack
Unauthorized connection attempt detected from IP address 183.80.122.207 to port 23
2019-12-31 22:07:49
144.217.85.239 attackbotsspam
Unauthorized connection attempt detected from IP address 144.217.85.239 to port 3727
2019-12-31 22:14:07
118.140.22.45 attack
Unauthorized connection attempt detected from IP address 118.140.22.45 to port 1433
2019-12-31 22:23:26
218.92.0.201 attackbotsspam
Unauthorized connection attempt detected from IP address 218.92.0.201 to port 22
2019-12-31 22:37:58
182.103.12.199 attackspambots
Unauthorized connection attempt detected from IP address 182.103.12.199 to port 445
2019-12-31 22:10:09
91.6.34.11 attackbotsspam
Lines containing failures of 91.6.34.11
Dec 31 07:16:07 mx-in-02 sshd[20848]: Invalid user pi from 91.6.34.11 port 37136
Dec 31 07:16:07 mx-in-02 sshd[20847]: Invalid user pi from 91.6.34.11 port 37130
Dec 31 07:16:07 mx-in-02 sshd[20848]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.6.34.11 
Dec 31 07:16:07 mx-in-02 sshd[20847]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.6.34.11 


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=91.6.34.11
2019-12-31 21:55:20
112.54.87.36 attack
Unauthorized connection attempt detected from IP address 112.54.87.36 to port 1433
2019-12-31 22:26:44
59.63.150.65 attackspambots
Unauthorized connection attempt detected from IP address 59.63.150.65 to port 445
2019-12-31 21:59:13
223.72.98.2 attack
Unauthorized connection attempt detected from IP address 223.72.98.2 to port 3389
2019-12-31 22:01:53
210.5.156.196 attackbotsspam
12/31/2019-14:23:08.750010 210.5.156.196 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-12-31 22:06:03
193.169.253.86 attack
Unauthorized connection attempt detected from IP address 193.169.253.86 to port 8545
2019-12-31 22:06:49

Recently Reported IPs

34.239.122.61 194.187.178.59 194.187.178.228 20.29.22.204
2606:4700:10::6814:6891 2606:4700:10::6816:4196 2606:4700:10::6814:9584 20.215.53.78
120.55.61.72 39.163.30.121 27.216.236.233 223.89.222.166
223.74.29.186 223.73.183.102 183.209.229.65 183.198.226.206
178.128.93.199 1.30.31.36 125.44.140.12 117.189.16.183