appsally.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafe13 years old
40
appsally.com was registered on 8 Jun 2013 via MarkMonitor Inc. and the registry expiry is 8 Jun 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/appsally.com.
appsally.com publishes 4 nameservers. DNSSEC is not signed.
appsally.com has 1 IPv4 address (3.33.139.32). The geolocation database places 3.33.139.32 in Montreal, Canada.
No safety warning was recorded for appsally.com in the checks that ran.
Domain · RDAP/WHOIS
appsally.com was registered on 8 Jun 2013 via MarkMonitor Inc.. The registry returned 3 status values and 4 nameservers from https://rdap.verisign.com/com/v1/domain/appsally.com.
| Registered | since 8 Jun 2013 |
|---|---|
| Created | 8 June 2013 |
| Updated | 30 April 2026 |
| Expires | 8 June 2027 |
| Registrar | MarkMonitor Inc. |
| Status | client delete prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/appsally.com |
appsally.com carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
appsally.com carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
appsally.com carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver ns1.markmonitor.com is published for appsally.com in the registration record from https://rdap.verisign.com/com/v1/domain/appsally.com.
Nameserver ns3.markmonitor.com is published for appsally.com in the registration record from https://rdap.verisign.com/com/v1/domain/appsally.com.
Nameserver ns4.markmonitor.com is published for appsally.com in the registration record from https://rdap.verisign.com/com/v1/domain/appsally.com.
Nameserver ns5.markmonitor.com is published for appsally.com in the registration record from https://rdap.verisign.com/com/v1/domain/appsally.com.
DNS
appsally.com has 1 address record, 0 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 3.33.139.32 |
|---|---|
| AAAA | — |
| NS | ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com |
| MX | — |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at appsally.com is "v=spf1 -all".
The DMARC text record at _dmarc.appsally.com is "v=DMARC1; p=reject; rua=mailto:[email protected]; ruf=mailto:[email protected]".
IPv4 address 3.33.139.32 answers for appsally.com at resolver 1.1.1.1:53.
Hosting and geo
appsally.com is placed in Montreal, Canada by the local geolocation database (db-ip).
| Address | 3.33.139.32 |
|---|---|
| Country | Canada |
| City | Montreal |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for appsally.com on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp 3.33.139.32:443: i/o timeout
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
context deadline exceeded
Security
Family DNS for appsally.com is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Score breakdown
Availability 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 0 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 10 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: geo city changed from empty to Montreal.
- October 2026: geo country changed from empty to Canada.
Questions
Is appsally.com safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts appsally.com?
appsally.com is placed in Montreal, Canada.
When does appsally.com expire?
appsally.com expires on 8 June 2027 according to https://rdap.verisign.com/com/v1/domain/appsally.com.
Who owns appsally.com?
The registry did not return a person or a company for appsally.com. RDAP often redacts the registrant. The registrar on file is MarkMonitor Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/appsally.com at 2026-10-30T13:45:10Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:45:10Z
- TLS source tls:443 at 2026-10-30T13:45:10Z
- HTTP source https://appsally.com/ at 2026-10-30T13:45:10Z
- Tech source not available at 2026-10-30T13:45:10Z
- Geo source db-ip at 2026-10-30T13:45:10Z
- Safety source family DNS and local lists at 2026-10-30T13:45:10Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
How to read this report
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.