heartsender.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blocked7 years old
5
heartsender.com was registered on 1 Nov 2019 via Internet Domain Service BS Corp and the registry expiry is 1 Nov 2026. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/heartsender.com.
Domain · RDAP/WHOIS
heartsender.com was registered on 1 Nov 2019 via Internet Domain Service BS Corp. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/heartsender.com.
| Registered | since 1 Nov 2019 |
|---|---|
| Created | 1 November 2019 |
| Updated | 2 November 2025 |
| Expires | 1 November 2026 |
| Registrar | Internet Domain Service BS Corp |
| Status | client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited |
| Nameservers | ns1.fbi.seized.gov, ns2.fbi.seized.gov |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/heartsender.com |
heartsender.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.
heartsender.com carries the status "server delete prohibited". The registry itself is refusing deletes. This lock is not one the registrar can clear alone.
heartsender.com carries the status "server transfer prohibited". The registry itself is refusing transfers. The name stays at the current registrar while the status remains.
heartsender.com carries the status "server update prohibited". The registry itself is refusing updates to the domain object.
Nameserver ns1.fbi.seized.gov is published for heartsender.com in the registration record from https://rdap.verisign.com/com/v1/domain/heartsender.com.
Nameserver ns2.fbi.seized.gov is published for heartsender.com in the registration record from https://rdap.verisign.com/com/v1/domain/heartsender.com.
DNS
heartsender.com has 0 address records, 0 mail exchangers and 0 nameservers, measured at 1.1.1.1:53.
| A | — |
|---|---|
| AAAA | — |
| NS | — |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
Hosting and geo
Geolocation for heartsender.com is not available. No local city or ASN database is installed, so this report does not guess a country.
| Geolocation | not available |
|---|---|
| Source | maxmind |
SSL/TLS
No TLS certificate was read for heartsender.com on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp: lookup heartsender.com on 46.38.225.230:53: server misbehaving
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 |
|---|
Get "https://heartsender.com/": dial tcp: lookup heartsender.com on 46.38.225.230:53: server misbehaving
Security
Family DNS for heartsender.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 heartsender.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 0 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 0 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
First checked on 30 October 2026; changes will appear here.
Questions
Is heartsender.com safe?
Cloudflare family DNS returned a block for heartsender.com. That resolver covers adult and malware names.
Who hosts heartsender.com?
The host network is not available without a local geolocation database.
When does heartsender.com expire?
heartsender.com expires on 1 November 2026 according to https://rdap.verisign.com/com/v1/domain/heartsender.com.
Who owns heartsender.com?
The registry did not return a person or a company for heartsender.com. RDAP often redacts the registrant. The registrar on file is Internet Domain Service BS Corp.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/heartsender.com at 2026-10-30T13:57:22Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:57:22Z
- TLS source tls:443 at 2026-10-30T13:57:22Z
- HTTP source https://heartsender.com/ at 2026-10-30T13:57:22Z
- Tech source not available at 2026-10-30T13:57:22Z
- Geo source db-ip at 2026-10-30T13:57:22Z
- Safety source family DNS and local lists at 2026-10-30T13:57:22Z
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.