boylove.cc
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 49 days left6 years oldTranco #21298
50
boylove.cc was registered on 10 Apr 2020 via GoDaddy.com, LLC and the registry expiry is 10 Apr 2027. WHOIS data came from RDAP at https://tld-rdap.verisign.com/cc/v1/domain/boylove.cc.
boylove.cc publishes 2 nameservers. DNSSEC is not signed.
boylove.cc has 3 IPv4 addresses (104.26.12.246, 104.26.13.246, 172.67.72.188) and 3 IPv6 addresses (2606:4700:20::681a:cf6, 2606:4700:20::681a:df6, 2606:4700:20::ac43:48bc). The geolocation database places 104.26.12.246 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 49 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Google Analytics, Google Tag Manager, Headroom.js, OWL Carousel, SweetAlert2, TrafficStars and jQuery. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
boylove.cc was registered on 10 Apr 2020 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://tld-rdap.verisign.com/cc/v1/domain/boylove.cc.
| Registered | since 10 Apr 2020 |
|---|---|
| Created | 10 April 2020 |
| Updated | 10 April 2026 |
| Expires | 10 April 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ethan.ns.cloudflare.com, gigi.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://tld-rdap.verisign.com/cc/v1/domain/boylove.cc |
boylove.cc 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.
boylove.cc 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.
boylove.cc 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.
boylove.cc 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 ethan.ns.cloudflare.com is published for boylove.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/boylove.cc.
Nameserver gigi.ns.cloudflare.com is published for boylove.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/boylove.cc.
DNS
boylove.cc has 6 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.26.12.246, 104.26.13.246, 172.67.72.188 |
|---|---|
| AAAA | 2606:4700:20::681a:cf6, 2606:4700:20::681a:df6, 2606:4700:20::ac43:48bc |
| NS | ethan.ns.cloudflare.com, gigi.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.26.12.246 answers for boylove.cc at resolver 1.1.1.1:53.
IPv4 address 104.26.13.246 answers for boylove.cc at resolver 1.1.1.1:53.
IPv4 address 172.67.72.188 answers for boylove.cc at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:cf6 answers for boylove.cc at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:df6 answers for boylove.cc at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::ac43:48bc answers for boylove.cc at resolver 1.1.1.1:53.
Hosting and geo
boylove.cc is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.26.12.246 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for boylove.cc is valid, with 49 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | boylove.cc |
| Valid from | 20 September 2026 |
| Valid until | 19 December 2026 |
| Days left | 49 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.boylove.cc, boylove.cc.
Tech stack
Tech detection checked the fetched homepage and named 8 products. Source: wappalyzergo.
- Cloudflare · CDN
- Google Analytics · Analytics
- Google Tag Manager · Tag managers
- Headroom.js · Widgets, JavaScript libraries
- OWL Carousel · JavaScript libraries
- SweetAlert2 · JavaScript libraries
- TrafficStars · Advertising
- jQuery · JavaScript libraries
Cloudflare is filed under CDN.
Google Analytics is filed under Analytics.
Google Tag Manager is filed under Tag managers.
Headroom.js is filed under Widgets, JavaScript libraries.
OWL Carousel is filed under JavaScript libraries.
SweetAlert2 is filed under JavaScript libraries.
TrafficStars is filed under Advertising.
jQuery is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 284 ms. The target title is 27 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 284 ms |
| Title length | 27 yes |
| Quoted title | "香香腐宅BoyLove│耽美漫畫-最新最全的BL腐漫網" |
| Meta description | "香香腐宅是一個專注於耽美漫畫與小說的網站，匯聚了各式風格的BL作品，從校園戀愛到甜蜜故事應有盡有。網站致力於提供讀者高品質的耽美作品體驗，成為耽美愛好者們的聚集地。" yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | http://boylove.cc/ |
| Language | — |
| Links | 49 |
| Images | 89 |
| 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 boylove.cc 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 boylove.cc. 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 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 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 boylove.cc safe?
Cloudflare family DNS returned a block for boylove.cc. That resolver covers adult and malware names.
Who hosts boylove.cc?
boylove.cc is placed in Toronto, Canada.
When does boylove.cc expire?
boylove.cc expires on 10 April 2027 according to https://tld-rdap.verisign.com/cc/v1/domain/boylove.cc.
Who owns boylove.cc?
The registry did not return a person or a company for boylove.cc. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://tld-rdap.verisign.com/cc/v1/domain/boylove.cc at 2026-10-30T13:33:38Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:33:38Z
- TLS source tls:443 at 2026-10-30T13:33:38Z
- HTTP source https://boylove.cc/ at 2026-10-30T13:33:38Z
- Tech source wappalyzergo at 2026-10-30T13:33:38Z
- Geo source db-ip at 2026-10-30T13:33:38Z
- Safety source family DNS and local lists at 2026-10-30T13:33:38Z
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.