finestories.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 75 days left16 years old
90
finestories.com was registered on 26 Apr 2010 via GoDaddy Online Services Cayman Islands Ltd. and the registry expiry is 26 Apr 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/finestories.com.
finestories.com publishes 2 nameservers. DNSSEC is not signed.
finestories.com has 1 IPv4 address (23.239.12.219) and 1 IPv6 address (2600:3c03:e000:19e::3). The geolocation database places 23.239.12.219 in Hanover (Cedar Knolls), United States.
The TLS certificate from YE2 is valid and has 75 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Apache HTTP Server, Fedora, HSTS, Moneris, OpenSSL and PHP. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for finestories.com in the checks that ran.
Domain · RDAP/WHOIS
finestories.com was registered on 26 Apr 2010 via GoDaddy Online Services Cayman Islands Ltd.. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/finestories.com.
| Registered | since 26 Apr 2010 |
|---|---|
| Created | 26 April 2010 |
| Updated | 27 April 2026 |
| Expires | 26 April 2027 |
| Registrar | GoDaddy Online Services Cayman Islands Ltd. |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns19.domaincontrol.com, ns20.domaincontrol.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/finestories.com |
finestories.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.
finestories.com carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
finestories.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.
finestories.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 ns19.domaincontrol.com is published for finestories.com in the registration record from https://rdap.verisign.com/com/v1/domain/finestories.com.
Nameserver ns20.domaincontrol.com is published for finestories.com in the registration record from https://rdap.verisign.com/com/v1/domain/finestories.com.
DNS
finestories.com has 2 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 23.239.12.219 |
|---|---|
| AAAA | 2600:3c03:e000:19e::3 |
| NS | ns19.domaincontrol.com, ns20.domaincontrol.com |
| MX | mail1.wlpubmail.com (10) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at finestories.com is "v=spf1 a:mail.wlpubmail.com a:mail1.wlpubmail.com ip4:45.33.67.140 ip4:172.105.107.207 ip6:2600:3c04::f03c:94ff:fefe:ebdf -all".
The DMARC text record at _dmarc.finestories.com is "v=DMARC1; p=quarantine; pct=100".
IPv4 address 23.239.12.219 answers for finestories.com at resolver 1.1.1.1:53.
IPv6 address 2600:3c03:e000:19e::3 answers for finestories.com at resolver 1.1.1.1:53.
Mail exchanger mail1.wlpubmail.com has preference 10.
A random label under finestories.com also resolved, which means wildcard DNS is on.
Hosting and geo
finestories.com is placed in Hanover (Cedar Knolls), United States by the local geolocation database (db-ip).
| Address | 23.239.12.219 |
|---|---|
| Country | United States |
| City | Hanover (Cedar Knolls) |
| Source | db-ip |
SSL/TLS
The certificate for finestories.com is valid, with 75 days left and 11 subject alternative names. Source: tls:443.
| Issuer | YE2 |
|---|---|
| Subject | finestories.com |
| Valid from | 16 October 2026 |
| Valid until | 14 January 2027 |
| Days left | 75 |
| SAN count | 11 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: finestories.com, hotsexstories.com, indianerotica.com, pmduck.com, scifistories.com, storyroom.com, www.hotsexstories.com, www.indianerotica.com, www.pmduck.com, www.scifistories.com, www.storyroom.com.
Tech stack
Tech detection checked the fetched homepage and named 6 products. Source: wappalyzergo.
- Apache HTTP Server · Web servers
- Fedora · Operating systems
- HSTS · Security
- Moneris · Payment processors
- OpenSSL · Web server extensions
- PHP · Programming languages
Apache HTTP Server is filed under Web servers.
Fedora is filed under Operating systems.
HSTS is filed under Security.
Moneris is filed under Payment processors.
OpenSSL is filed under Web server extensions.
PHP is filed under Programming languages.
On-page checks
The homepage returned HTTP 200 in 83 ms. The target title is 9 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 83 ms |
| Title length | 9 yes |
| Quoted title | "StoryRoom" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | yes |
| X-Frame-Options | deny |
| Robots meta | INDEX, FOLLOW |
| Canonical | https://storyroom.com/ |
| Language | en |
| Links | 331 |
| Images | 1 |
| Favicon | yes |
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 finestories.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 25 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 10 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 Hanover (Cedar Knolls).
- October 2026: geo country changed from empty to United States.
Questions
Is finestories.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 finestories.com?
finestories.com is placed in Hanover (Cedar Knolls), United States.
When does finestories.com expire?
finestories.com expires on 26 April 2027 according to https://rdap.verisign.com/com/v1/domain/finestories.com.
Who owns finestories.com?
The registry did not return a person or a company for finestories.com. RDAP often redacts the registrant. The registrar on file is GoDaddy Online Services Cayman Islands Ltd..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/finestories.com at 2026-10-30T13:54:40Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:54:40Z
- TLS source tls:443 at 2026-10-30T13:54:40Z
- HTTP source https://finestories.com/ at 2026-10-30T13:54:40Z
- Tech source wappalyzergo at 2026-10-30T13:54:40Z
- Geo source db-ip at 2026-10-30T13:54:40Z
- Safety source family DNS and local lists at 2026-10-30T13:54:40Z
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.