ahashare.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blocked18 years old
20
ahashare.com was registered on 27 Apr 2008 via Tecnologia, Desarrollo Y Mercado S. de R.L. de C.V. and the registry expiry is 27 Apr 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/ahashare.com.
ahashare.com publishes 2 nameservers. DNSSEC is not signed.
ahashare.com has 1 IPv4 address (162.4.84.215). The geolocation database places 162.4.84.215 in Los Angeles, United States.
Domain · RDAP/WHOIS
ahashare.com was registered on 27 Apr 2008 via Tecnologia, Desarrollo Y Mercado S. de R.L. de C.V.. The registry returned 2 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/ahashare.com.
| Registered | since 27 Apr 2008 |
|---|---|
| Created | 27 April 2008 |
| Updated | 27 April 2026 |
| Expires | 27 April 2027 |
| Registrar | Tecnologia, Desarrollo Y Mercado S. de R.L. de C.V. |
| Status | client delete prohibited, client transfer prohibited |
| Nameservers | a.2ns.net, b.2ns.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/ahashare.com |
ahashare.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.
ahashare.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.
Nameserver a.2ns.net is published for ahashare.com in the registration record from https://rdap.verisign.com/com/v1/domain/ahashare.com.
Nameserver b.2ns.net is published for ahashare.com in the registration record from https://rdap.verisign.com/com/v1/domain/ahashare.com.
DNS
ahashare.com has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 162.4.84.215 |
|---|---|
| AAAA | — |
| NS | ns4.dnsauthority.com, ns5.dnsauthority.com |
| MX | mail.hope-mail.com (1) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at ahashare.com is "v=spf1 ip6:fd18:d113:9bed::/48 -all".
IPv4 address 162.4.84.215 answers for ahashare.com at resolver 1.1.1.1:53.
Mail exchanger mail.hope-mail.com has preference 1.
A random label under ahashare.com also resolved, which means wildcard DNS is on.
Hosting and geo
ahashare.com is placed in Los Angeles, United States by the local geolocation database (db-ip).
| Address | 162.4.84.215 |
|---|---|
| Country | United States |
| City | Los Angeles |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for ahashare.com on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp: lookup ahashare.com: 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 ahashare.com is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for ahashare.com. That resolver covers adult and malware names.
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 5 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 0 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: dns wildcard changed from false to true.
- October 2026: geo city changed from empty to Los Angeles.
- October 2026: geo country changed from empty to United States.
Questions
Is ahashare.com safe?
Cloudflare family DNS returned a block for ahashare.com. That resolver covers adult and malware names.
Who hosts ahashare.com?
ahashare.com is placed in Los Angeles, United States.
When does ahashare.com expire?
ahashare.com expires on 27 April 2027 according to https://rdap.verisign.com/com/v1/domain/ahashare.com.
Who owns ahashare.com?
The registry did not return a person or a company for ahashare.com. RDAP often redacts the registrant. The registrar on file is Tecnologia, Desarrollo Y Mercado S. de R.L. de C.V..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/ahashare.com at 2026-10-30T13:43:26Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:43:26Z
- TLS source tls:443 at 2026-10-30T13:43:26Z
- HTTP source https://ahashare.com/ at 2026-10-30T13:43:26Z
- Tech source not available at 2026-10-30T13:43:26Z
- Geo source db-ip at 2026-10-30T13:43:26Z
- Safety source family DNS and local lists at 2026-10-30T13:43:26Z
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.