boundstories.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
55
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
55
boundstories.net was registered on 8 Nov 2008 via NameCheap, Inc. and the registry expiry is 8 Nov 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/boundstories.net.
boundstories.net publishes 4 nameservers. DNSSEC is not signed.
boundstories.net has 4 IPv4 addresses (18.245.86.30, 18.245.86.42, 18.245.86.57, 18.245.86.87) and 8 IPv6 addresses (2600:9000:28dc:4200:1b:77d7:e400:93a1, 2600:9000:28dc:4600:1b:77d7:e400:93a1, 2600:9000:28dc:4e00:1b:77d7:e400:93a1, 2600:9000:28dc:a400:1b:77d7:e400:93a1, 2600:9000:28dc:aa00:1b:77d7:e400:93a1, 2600:9000:28dc:ac00:1b:77d7:e400:93a1, 2600:9000:28dc:de00:1b:77d7:e400:93a1, 2600:9000:28dc:f400:1b:77d7:e400:93a1). The geolocation database places 18.245.86.30 in Frankfurt am Main, Germany.
The TLS certificate from Amazon RSA 2048 M04 is valid and has 173 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Amazon CloudFront, Amazon Web Services, HTTP/3, Nginx and PHP. The fingerprints ran on the homepage that was already downloaded.
boundstories.net was registered on 8 Nov 2008 via NameCheap, Inc.. The registry returned 1 status value and 4 nameservers from https://rdap.verisign.com/net/v1/domain/boundstories.net.
| Registered | since 8 Nov 2008 |
|---|---|
| Created | 8 November 2008 |
| Updated | 9 October 2026 |
| Expires | 8 November 2027 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | ns-1496.awsdns-59.org, ns-1685.awsdns-18.co.uk, ns-277.awsdns-34.com, ns-975.awsdns-57.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/boundstories.net |
boundstories.net 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 ns-1496.awsdns-59.org is published for boundstories.net in the registration record from https://rdap.verisign.com/net/v1/domain/boundstories.net.
Nameserver ns-1685.awsdns-18.co.uk is published for boundstories.net in the registration record from https://rdap.verisign.com/net/v1/domain/boundstories.net.
Nameserver ns-277.awsdns-34.com is published for boundstories.net in the registration record from https://rdap.verisign.com/net/v1/domain/boundstories.net.
Nameserver ns-975.awsdns-57.net is published for boundstories.net in the registration record from https://rdap.verisign.com/net/v1/domain/boundstories.net.
boundstories.net has 12 address records, 1 mail exchanger and 4 nameservers, measured at 1.1.1.1:53.
| A | 18.245.86.30, 18.245.86.42, 18.245.86.57, 18.245.86.87 |
|---|---|
| AAAA | 2600:9000:28dc:4200:1b:77d7:e400:93a1, 2600:9000:28dc:4600:1b:77d7:e400:93a1, 2600:9000:28dc:4e00:1b:77d7:e400:93a1, 2600:9000:28dc:a400:1b:77d7:e400:93a1, 2600:9000:28dc:aa00:1b:77d7:e400:93a1, 2600:9000:28dc:ac00:1b:77d7:e400:93a1, 2600:9000:28dc:de00:1b:77d7:e400:93a1, 2600:9000:28dc:f400:1b:77d7:e400:93a1 |
| NS | ns-1496.awsdns-59.org, ns-1685.awsdns-18.co.uk, ns-277.awsdns-34.com, ns-975.awsdns-57.net |
| MX | smtp.google.com (1) Google |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at boundstories.net is "v=spf1 mx ip4:77.232.64.0/19 ip4:92.61.144.0/20 +all".
IPv4 address 18.245.86.30 answers for boundstories.net at resolver 1.1.1.1:53.
IPv4 address 18.245.86.42 answers for boundstories.net at resolver 1.1.1.1:53.
IPv4 address 18.245.86.57 answers for boundstories.net at resolver 1.1.1.1:53.
IPv4 address 18.245.86.87 answers for boundstories.net at resolver 1.1.1.1:53.
IPv6 address 2600:9000:28dc:4200:1b:77d7:e400:93a1 answers for boundstories.net at resolver 1.1.1.1:53.
IPv6 address 2600:9000:28dc:4600:1b:77d7:e400:93a1 answers for boundstories.net at resolver 1.1.1.1:53.
IPv6 address 2600:9000:28dc:4e00:1b:77d7:e400:93a1 answers for boundstories.net at resolver 1.1.1.1:53.
IPv6 address 2600:9000:28dc:a400:1b:77d7:e400:93a1 answers for boundstories.net at resolver 1.1.1.1:53.
IPv6 address 2600:9000:28dc:aa00:1b:77d7:e400:93a1 answers for boundstories.net at resolver 1.1.1.1:53.
IPv6 address 2600:9000:28dc:ac00:1b:77d7:e400:93a1 answers for boundstories.net at resolver 1.1.1.1:53.
IPv6 address 2600:9000:28dc:de00:1b:77d7:e400:93a1 answers for boundstories.net at resolver 1.1.1.1:53.
IPv6 address 2600:9000:28dc:f400:1b:77d7:e400:93a1 answers for boundstories.net at resolver 1.1.1.1:53.
Mail exchanger smtp.google.com has preference 1. The host is recognised as Google.
boundstories.net is placed in Frankfurt am Main, Germany by the local geolocation database (db-ip).
| Address | 18.245.86.30 |
|---|---|
| Country | Germany |
| City | Frankfurt am Main |
| Source | db-ip |
The certificate for boundstories.net is valid, with 173 days left and 2 subject alternative names. Source: tls:443.
| Issuer | Amazon RSA 2048 M04 |
|---|---|
| Subject | boundstories.net |
| Valid from | 7 October 2026 |
| Valid until | 22 April 2027 |
| Days left | 173 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: boundstories.net, www.boundstories.net.
Tech detection checked the fetched homepage and named 5 products. Source: wappalyzergo.
Amazon CloudFront is filed under CDN.
Amazon Web Services is filed under PaaS.
HTTP/3 is filed under Miscellaneous.
Nginx is filed under Web servers, Reverse proxies.
PHP is filed under Programming languages.
The homepage returned HTTP 200 in 5 ms. The target title is 60 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 5 ms |
| Title length | 60 yes |
| Quoted title | "Welcome to Boundstories.net | Bound Stories | Gromet's Plaza" |
| Meta description | "Bound Stories is a free bondage stories story website, part of Gromet's Plaza, featuring bondage, fetish, BDSM, self bondage type stories." yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 5 |
| Images | 2 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for boundstories.net 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 boundstories.net. 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.
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 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.
Cloudflare family DNS returned a block for boundstories.net. That resolver covers adult and malware names.
boundstories.net is placed in Frankfurt am Main, Germany.
boundstories.net expires on 8 November 2027 according to https://rdap.verisign.com/net/v1/domain/boundstories.net.
The registry did not return a person or a company for boundstories.net. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
No other indexable reports share this TLD, host, or registrar yet.
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.
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.