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

Region: Ohio

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:       18.32.0.0 - 18.255.255.255
CIDR:           18.64.0.0/10, 18.32.0.0/11, 18.128.0.0/9
NetName:        AT-88-Z
NetHandle:      NET-18-32-0-0-1
Parent:         NET18 (NET-18-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       
Organization:   Amazon Technologies Inc. (AT-88-Z)
RegDate:        2019-10-07
Updated:        2021-02-10
Ref:            https://rdap.arin.net/registry/ip/18.32.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

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

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

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


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

;; QUESTION SECTION:
;18.219.106.116.			IN	A

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

;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jun 12 05:30:06 CST 2026
;; MSG SIZE  rcvd: 107
Host info
116.106.219.18.in-addr.arpa domain name pointer ec2-18-219-106-116.us-east-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
116.106.219.18.in-addr.arpa	name = ec2-18-219-106-116.us-east-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
154.151.61.39 attackbotsspam
port scan
2020-05-08 15:28:13
194.26.29.114 attackbots
May  8 09:13:38 debian-2gb-nbg1-2 kernel: \[11180900.597264\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=194.26.29.114 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=22503 PROTO=TCP SPT=42627 DPT=5394 WINDOW=1024 RES=0x00 SYN URGP=0
2020-05-08 15:35:05
31.184.215.44 attackbots
May  8 09:41:47 debian-2gb-nbg1-2 kernel: \[11182589.498460\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=31.184.215.44 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=28742 PROTO=TCP SPT=56606 DPT=12345 WINDOW=1024 RES=0x00 SYN URGP=0
2020-05-08 15:54:39
103.139.43.198 attackspam
Port scan on 3 port(s): 3151 3384 3448
2020-05-08 15:40:45
35.184.155.136 attackspam
$f2bV_matches
2020-05-08 15:38:43
91.204.248.42 attackspambots
$f2bV_matches
2020-05-08 15:21:22
118.45.130.170 attack
May  8 09:02:26 rotator sshd\[21298\]: Invalid user julia from 118.45.130.170May  8 09:02:28 rotator sshd\[21298\]: Failed password for invalid user julia from 118.45.130.170 port 41313 ssh2May  8 09:04:35 rotator sshd\[21320\]: Invalid user bic from 118.45.130.170May  8 09:04:37 rotator sshd\[21320\]: Failed password for invalid user bic from 118.45.130.170 port 57777 ssh2May  8 09:06:39 rotator sshd\[22078\]: Invalid user gaowen from 118.45.130.170May  8 09:06:41 rotator sshd\[22078\]: Failed password for invalid user gaowen from 118.45.130.170 port 45965 ssh2
...
2020-05-08 15:56:14
115.84.92.32 attackbots
Dovecot Invalid User Login Attempt.
2020-05-08 16:01:46
119.29.2.157 attackspam
Wordpress malicious attack:[sshd]
2020-05-08 15:26:16
37.49.226.235 attackbotsspam
Unauthorized connection attempt detected from IP address 37.49.226.235 to port 81
2020-05-08 15:19:53
124.195.207.34 attack
20/5/7@23:54:11: FAIL: Alarm-Telnet address from=124.195.207.34
...
2020-05-08 15:52:22
61.133.232.252 attackbotsspam
May  8 00:49:21 firewall sshd[26011]: Invalid user el from 61.133.232.252
May  8 00:49:22 firewall sshd[26011]: Failed password for invalid user el from 61.133.232.252 port 30545 ssh2
May  8 00:54:10 firewall sshd[26148]: Invalid user postgres from 61.133.232.252
...
2020-05-08 15:53:44
45.116.117.33 attackbots
DATE:2020-05-08 05:54:13, IP:45.116.117.33, PORT:1433 MSSQL brute force auth on honeypot server (epe-honey1-hq)
2020-05-08 15:49:46
115.254.63.52 attack
1588913241 - 05/08/2020 06:47:21 Host: 115.254.63.52/115.254.63.52 Port: 22 TCP Blocked
2020-05-08 15:55:02
35.194.131.64 attackbots
May  8 07:31:08 inter-technics sshd[5659]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.194.131.64  user=root
May  8 07:31:11 inter-technics sshd[5659]: Failed password for root from 35.194.131.64 port 51280 ssh2
May  8 07:37:52 inter-technics sshd[6275]: Invalid user anurag from 35.194.131.64 port 35630
May  8 07:37:52 inter-technics sshd[6275]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.194.131.64
May  8 07:37:52 inter-technics sshd[6275]: Invalid user anurag from 35.194.131.64 port 35630
May  8 07:37:54 inter-technics sshd[6275]: Failed password for invalid user anurag from 35.194.131.64 port 35630 ssh2
...
2020-05-08 15:27:16

Recently Reported IPs

185.226.197.29 129.226.94.52 165.232.118.73 92.112.243.6
2606:4700:10::6816:3614 8.216.88.216 66.249.78.5 182.16.91.238
119.42.149.26 103.116.123.109 20.215.49.97 182.16.91.202
2606:4700:10::6814:5356 18.97.26.85 2606:4700:10::6814:9793 116.76.194.117
207.154.211.43 124.71.175.215 118.100.233.111 103.116.123.205