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-2025, American Registry for Internet Numbers, Ltd.
#



# start

NetRange:       44.192.0.0 - 44.255.255.255
CIDR:           44.192.0.0/10
NetName:        AMAZO-4
NetHandle:      NET-44-192-0-0-1
Parent:         NET44 (NET-44-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       
Organization:   Amazon.com, Inc. (AMAZO-4)
RegDate:        2019-07-18
Updated:        2019-07-18
Ref:            https://rdap.arin.net/registry/ip/44.192.0.0



OrgName:        Amazon.com, Inc.
OrgId:          AMAZO-4
Address:        Amazon Web Services, Inc.
Address:        P.O. Box 81226
City:           Seattle
StateProv:      WA
PostalCode:     98108-1226
Country:        US
RegDate:        2005-09-29
Updated:        2022-09-30
Comment:        For details of this service please see
Comment:        http://ec2.amazonaws.com
Ref:            https://rdap.arin.net/registry/entity/AMAZO-4


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

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

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

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

# end


# start

NetRange:       44.192.0.0 - 44.223.255.255
CIDR:           44.192.0.0/11
NetName:        AMAZON-IAD
NetHandle:      NET-44-192-0-0-2
Parent:         AMAZO-4 (NET-44-192-0-0-1)
NetType:        Reallocated
OriginAS:       
Organization:   Amazon Data Services Northern Virginia (ADSN-1)
RegDate:        2019-08-01
Updated:        2019-08-01
Ref:            https://rdap.arin.net/registry/ip/44.192.0.0



OrgName:        Amazon Data Services Northern Virginia
OrgId:          ADSN-1
Address:        13200 Woodland Park Road
City:           Herndon
StateProv:      VA
PostalCode:     20171
Country:        US
RegDate:        2018-04-25
Updated:        2025-08-14
Ref:            https://rdap.arin.net/registry/entity/ADSN-1


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

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

# end



#
# 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-2025, American Registry for Internet Numbers, Ltd.
#
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 44.220.48.213
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21719
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;44.220.48.213.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Dec 01 10:00:29 CST 2025
;; MSG SIZE  rcvd: 106
Host info
213.48.220.44.in-addr.arpa domain name pointer ec2-44-220-48-213.compute-1.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
213.48.220.44.in-addr.arpa	name = ec2-44-220-48-213.compute-1.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
152.136.194.13 attack
port scan and connect, tcp 80 (http)
2020-06-25 06:47:43
120.220.242.30 attackspam
2020-06-24T20:32:23.396693shield sshd\[14087\]: Invalid user maruyama from 120.220.242.30 port 42331
2020-06-24T20:32:23.401988shield sshd\[14087\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.220.242.30
2020-06-24T20:32:25.123713shield sshd\[14087\]: Failed password for invalid user maruyama from 120.220.242.30 port 42331 ssh2
2020-06-24T20:35:34.799886shield sshd\[14248\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.220.242.30  user=root
2020-06-24T20:35:37.078358shield sshd\[14248\]: Failed password for root from 120.220.242.30 port 62167 ssh2
2020-06-25 06:56:05
185.153.196.230 attackspambots
...
2020-06-25 07:22:18
106.54.201.240 attackbotsspam
Jun 25 01:02:58 OPSO sshd\[8280\]: Invalid user lachlan from 106.54.201.240 port 39220
Jun 25 01:02:58 OPSO sshd\[8280\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.201.240
Jun 25 01:03:00 OPSO sshd\[8280\]: Failed password for invalid user lachlan from 106.54.201.240 port 39220 ssh2
Jun 25 01:07:45 OPSO sshd\[9215\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.201.240  user=ftp
Jun 25 01:07:47 OPSO sshd\[9215\]: Failed password for ftp from 106.54.201.240 port 60368 ssh2
2020-06-25 07:20:53
49.232.136.90 attackspambots
Jun 24 18:56:09 ny01 sshd[6661]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.136.90
Jun 24 18:56:11 ny01 sshd[6661]: Failed password for invalid user vit from 49.232.136.90 port 50022 ssh2
Jun 24 18:59:24 ny01 sshd[7188]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.136.90
2020-06-25 07:05:18
2600:9000:20a6:e400:10:ab99:6600:21 attack
Organized crime hosting edge cache http://d841gzbjvio48.cloudfront.net/35381/Screen%20Shot%202019-08-06%20at%2011.55.25%20AM.png
2020-06-25 07:23:40
111.161.74.125 attack
Failed password for invalid user puppet from 111.161.74.125 port 54752 ssh2
2020-06-25 07:20:01
61.167.79.203 attackspam
06/24/2020-19:07:47.292415 61.167.79.203 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2020-06-25 07:23:17
216.218.206.87 attackbots
Jun 24 22:35:28 debian-2gb-nbg1-2 kernel: \[15289593.019952\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=216.218.206.87 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=54321 PROTO=TCP SPT=48891 DPT=5900 WINDOW=65535 RES=0x00 SYN URGP=0
2020-06-25 07:01:30
149.28.60.171 attackspam
5060/udp
[2020-06-24]1pkt
2020-06-25 06:58:34
23.94.4.242 attack
(From eric@talkwithwebvisitor.com) Good day, 

My name is Eric and unlike a lot of emails you might get, I wanted to instead provide you with a word of encouragement – Congratulations

What for?  

Part of my job is to check out websites and the work you’ve done with docschiro.com definitely stands out. 

It’s clear you took building a website seriously and made a real investment of time and resources into making it top quality.

There is, however, a catch… more accurately, a question…

So when someone like me happens to find your site – maybe at the top of the search results (nice job BTW) or just through a random link, how do you know? 

More importantly, how do you make a connection with that person?

Studies show that 7 out of 10 visitors don’t stick around – they’re there one second and then gone with the wind.

Here’s a way to create INSTANT engagement that you may not have known about… 

Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visit
2020-06-25 07:03:14
45.165.215.83 attackspambots
(smtpauth) Failed SMTP AUTH login from 45.165.215.83 (BR/Brazil/-): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2020-06-25 03:37:48 plain authenticator failed for ([45.165.215.83]) [45.165.215.83]: 535 Incorrect authentication data (set_id=a.nazemi@safanicu.com)
2020-06-25 07:17:35
203.130.255.2 attackbots
Jun 25 00:10:33 meumeu sshd[1336821]: Invalid user r from 203.130.255.2 port 34312
Jun 25 00:10:33 meumeu sshd[1336821]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.130.255.2 
Jun 25 00:10:33 meumeu sshd[1336821]: Invalid user r from 203.130.255.2 port 34312
Jun 25 00:10:35 meumeu sshd[1336821]: Failed password for invalid user r from 203.130.255.2 port 34312 ssh2
Jun 25 00:12:41 meumeu sshd[1337049]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.130.255.2  user=root
Jun 25 00:12:43 meumeu sshd[1337049]: Failed password for root from 203.130.255.2 port 36432 ssh2
Jun 25 00:15:04 meumeu sshd[1337173]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.130.255.2  user=root
Jun 25 00:15:06 meumeu sshd[1337173]: Failed password for root from 203.130.255.2 port 38554 ssh2
Jun 25 00:17:34 meumeu sshd[1337363]: Invalid user sam from 203.130.255.2 port 40678
...
2020-06-25 06:47:21
37.144.45.243 attackbotsspam
445/tcp
[2020-06-24]1pkt
2020-06-25 06:51:23
77.42.124.107 attack
Automatic report - Port Scan Attack
2020-06-25 07:27:20

Recently Reported IPs

10.254.4.111 54.176.49.81 44.248.99.51 31.14.32.7
14.1.104.253 111.7.100.49 44.248.229.237 111.7.100.48
10.148.111.105 185.152.66.230 85.208.84.72 8.140.114.99
171.127.128.142 196.168.0.4 116.131.20.188 47.99.88.234
47.85.2.126 192.168.168.16 192.168.168.24 20.46.226.34