blushlove.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 63 days left11 years old
90
blushlove.com was registered on 18 Dec 2014 via GoDaddy.com, LLC and the registry expiry is 18 Dec 2026. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/blushlove.com.
blushlove.com publishes 2 nameservers. DNSSEC is not signed.
blushlove.com has 1 IPv4 address (23.227.38.65). The geolocation database places 23.227.38.65 in Toronto, Canada.
The TLS certificate from YE2 is valid and has 63 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, HSTS, HTTP/3, Klaviyo and Shopify. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for blushlove.com in the checks that ran.
Domain · RDAP/WHOIS
blushlove.com was registered on 18 Dec 2014 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/blushlove.com.
| Registered | since 18 Dec 2014 |
|---|---|
| Created | 18 December 2014 |
| Updated | 8 December 2025 |
| Expires | 18 December 2026 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns11.domaincontrol.com, ns12.domaincontrol.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/blushlove.com |
blushlove.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.
blushlove.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.
blushlove.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.
blushlove.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 ns11.domaincontrol.com is published for blushlove.com in the registration record from https://rdap.verisign.com/com/v1/domain/blushlove.com.
Nameserver ns12.domaincontrol.com is published for blushlove.com in the registration record from https://rdap.verisign.com/com/v1/domain/blushlove.com.
DNS
blushlove.com has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 23.227.38.65 |
|---|---|
| AAAA | — |
| NS | ns11.domaincontrol.com, ns12.domaincontrol.com |
| MX | blushlove-com.mail.protection.outlook.com (0) Microsoft 365 |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at blushlove.com is "v=spf1 include:spf.protection.outlook.com -all".
The DMARC text record at _dmarc.blushlove.com is "v=DMARC1; p=none;".
IPv4 address 23.227.38.65 answers for blushlove.com at resolver 1.1.1.1:53.
Mail exchanger blushlove-com.mail.protection.outlook.com has preference 0. The host is recognised as Microsoft 365.
Hosting and geo
blushlove.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 23.227.38.65 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for blushlove.com is valid, with 63 days left and 1 subject alternative name. Source: tls:443.
| Issuer | YE2 |
|---|---|
| Subject | blushlove.com |
| Valid from | 4 October 2026 |
| Valid until | 2 January 2027 |
| Days left | 63 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: blushlove.com.
Tech stack
Tech detection checked the fetched homepage and named 5 products. Source: wappalyzergo.
- Cloudflare · CDN
- HSTS · Security
- HTTP/3 · Miscellaneous
- Klaviyo · Marketing automation
- Shopify · Ecommerce, CMS
Cloudflare is filed under CDN.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
Klaviyo is filed under Marketing automation.
Shopify is filed under Ecommerce, CMS.
On-page checks
The homepage returned HTTP 200 in 99 ms. The target title is 11 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 99 ms |
| Title length | 11 yes |
| Quoted title | "– BlushLove" |
| Meta description | "Blush is a sexual health brand committed to the pursuit of pleasure with innovation, education, and inclusivity. Our mission is to enhance intimacy with thoughtful products designed to celebrate all bodies." yes |
| H1 count | 0 |
| HSTS | yes yes |
| CSP | yes |
| X-Frame-Options | DENY |
| Robots meta | — |
| Canonical | https://blushlove.com/password |
| Language | en |
| Links | 13 |
| Images | 6 |
| 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 blushlove.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 Toronto.
- October 2026: geo country changed from empty to Canada.
Questions
Is blushlove.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 blushlove.com?
blushlove.com is placed in Toronto, Canada.
When does blushlove.com expire?
blushlove.com expires on 18 December 2026 according to https://rdap.verisign.com/com/v1/domain/blushlove.com.
Who owns blushlove.com?
The registry did not return a person or a company for blushlove.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/blushlove.com at 2026-10-30T13:47:26Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:47:26Z
- TLS source tls:443 at 2026-10-30T13:47:26Z
- HTTP source https://blushlove.com/ at 2026-10-30T13:47:26Z
- Tech source wappalyzergo at 2026-10-30T13:47:26Z
- Geo source db-ip at 2026-10-30T13:47:26Z
- Safety source family DNS and local lists at 2026-10-30T13:47: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.