Appgiftdl.com was registered on gal communication on 14 November 2015.
The site just started on social networks.
The site receives 10,200 visitors every month, which put its worth at around $ approximately.
The website has a good alexa rank of 380,051.
The domain for the website was purchased through gal communication on 14 November 2015 (2 years ago) and will expire in 1 year 4 months.
Alexa Rank 380,051
Visitors 300 daily
Approx. Monthly Revenue $91
Text lanuage None
Family safe text Yes
The report was last updated on January 04, 2016.
If its not up to date, please click the update button for the same.
Social Network Presence
Following statistics represent appgiftdl.com activity on various social networks.
Find out about the infrastructure of appgiftdl.com, e.g. how the website works, what hardware and software it uses etc.
Email hosted by
Web Hosting Provider
Site Generating Software
SSL Certificate Issuer
Domain Registered by
These records can help to identify the owners of appgiftdl.com. You can contact the admins through the email present in these records.
14 November 2015
14 November 2016
Whois Server Version 2.0
Domain Name: APPGIFTDL.COM
Registrar: GAL COMMUNICATION (COMMUNIGAL) LTD.
Sponsoring Registrar IANA ID: 418
Whois Server: whois.communigal.net
Name Server: NS-1284.AWSDNS-32.ORG
Name Server: NS-1582.AWSDNS-05.CO.UK
Name Server: NS-466.AWSDNS-58.COM
Name Server: NS-642.AWSDNS-16.NET
Status: clientTransferProhibited Updated Date: 14-nov-2015
Creation Date: 14-nov-2015
Expiration Date: 14-nov-2016
For more information on Whois status codes, please visit
The Registry database contains ONLY .COM, .NET, .EDU domains and
Find out all the details about the IP address used by the website, including the nameservers and IP location.
No IP information found for the website!!
Following are the links associated with the homepage of the website.
Following information represents the extra metadata sent by the website servers on requesting the homepage of the website.
No HTTP Headers were found for appgiftdl.com, it could be because the site was offline when the report was created!