novelheart.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 403SafeSSL: 74 days left1 year old
65
novelheart.com was registered on 16 Jul 2025 via Dynadot Inc and the registry expiry is 16 Jul 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/novelheart.com.
novelheart.com publishes 2 nameservers. DNSSEC is not signed.
novelheart.com has 1 IPv4 address (52.20.84.62). The geolocation database places 52.20.84.62 in Ashburn, United States.
The TLS certificate from YE1 is valid and has 74 days left (TLS 1.3).
Tech detection named Cloudflare, Cloudflare Bot Management, HSTS and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for novelheart.com in the checks that ran.
Domain · RDAP/WHOIS
novelheart.com was registered on 16 Jul 2025 via Dynadot Inc. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/novelheart.com.
| Registered | since 16 Jul 2025 |
|---|---|
| Created | 16 July 2025 |
| Updated | 14 July 2026 |
| Expires | 16 July 2027 |
| Registrar | Dynadot Inc |
| Status | client transfer prohibited |
| Nameservers | ns1.atom.com, ns2.atom.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/novelheart.com |
novelheart.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 ns1.atom.com is published for novelheart.com in the registration record from https://rdap.verisign.com/com/v1/domain/novelheart.com.
Nameserver ns2.atom.com is published for novelheart.com in the registration record from https://rdap.verisign.com/com/v1/domain/novelheart.com.
DNS
novelheart.com has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 52.20.84.62 |
|---|---|
| AAAA | — |
| NS | ns1.atom.com, ns2.atom.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 52.20.84.62 answers for novelheart.com at resolver 1.1.1.1:53.
Hosting and geo
novelheart.com is placed in Ashburn, United States by the local geolocation database (db-ip).
| Address | 52.20.84.62 |
|---|---|
| Country | United States |
| City | Ashburn |
| Source | db-ip |
SSL/TLS
The certificate for novelheart.com is valid, with 74 days left and 1 subject alternative name. Source: tls:443.
| Issuer | YE1 |
|---|---|
| Subject | novelheart.com |
| Valid from | 16 October 2026 |
| Valid until | 14 January 2027 |
| Days left | 74 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: novelheart.com.
Tech stack
Tech detection checked the fetched homepage and named 4 products. Source: wappalyzergo.
- Cloudflare · CDN
- Cloudflare Bot Management · Security
- HSTS · Security
- HTTP/3 · Miscellaneous
Cloudflare is filed under CDN.
Cloudflare Bot Management is filed under Security.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 403 in 104 ms. The target title is 16 characters and the page has 0 H1 headings.
| Status | 403 |
|---|---|
| TTFB | 104 ms |
| Title length | 16 yes |
| Quoted title | "Just a moment..." |
| Meta description | none no |
| H1 count | 0 |
| HSTS | yes yes |
| CSP | yes |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | noindex,nofollow |
| Canonical | — |
| Language | en-US |
| Links | 0 |
| Images | 0 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for novelheart.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 | yes |
| CSP | yes |
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 20 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 15 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 Ashburn.
- October 2026: geo country changed from empty to United States.
Questions
Is novelheart.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 novelheart.com?
novelheart.com is placed in Ashburn, United States.
When does novelheart.com expire?
novelheart.com expires on 16 July 2027 according to https://rdap.verisign.com/com/v1/domain/novelheart.com.
Who owns novelheart.com?
The registry did not return a person or a company for novelheart.com. RDAP often redacts the registrant. The registrar on file is Dynadot Inc.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/novelheart.com at 2026-10-30T14:07:01Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:07:01Z
- TLS source tls:443 at 2026-10-30T14:07:01Z
- HTTP source https://novelheart.com/ at 2026-10-30T14:07:01Z
- Tech source wappalyzergo at 2026-10-30T14:07:01Z
- Geo source db-ip at 2026-10-30T14:07:01Z
- Safety source family DNS and local lists at 2026-10-30T14:07:01Z
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.