bdsmup.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
55
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
55
bdsmup.net was registered on 8 Apr 2020 via Tucows Domains Inc. and the registry expiry is 8 Apr 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/bdsmup.net.
bdsmup.net publishes 2 nameservers. DNSSEC is not signed.
bdsmup.net has 2 IPv4 addresses (188.114.96.3, 188.114.97.3) and 2 IPv6 addresses (2a06:98c1:3120::3, 2a06:98c1:3121::3). The geolocation database places 188.114.96.3 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 63 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Apache HTTP Server, Cloudflare, DataLife Engine, Google Analytics, HTTP/3, PHP and jQuery. The fingerprints ran on the homepage that was already downloaded.
bdsmup.net was registered on 8 Apr 2020 via Tucows Domains Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/net/v1/domain/bdsmup.net.
| Registered | since 8 Apr 2020 |
|---|---|
| Created | 8 April 2020 |
| Updated | 14 February 2026 |
| Expires | 8 April 2027 |
| Registrar | Tucows Domains Inc. |
| Status | active |
| Nameservers | austin.ns.cloudflare.com, melissa.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/bdsmup.net |
Nameserver austin.ns.cloudflare.com is published for bdsmup.net in the registration record from https://rdap.verisign.com/net/v1/domain/bdsmup.net.
Nameserver melissa.ns.cloudflare.com is published for bdsmup.net in the registration record from https://rdap.verisign.com/net/v1/domain/bdsmup.net.
bdsmup.net has 4 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.3, 188.114.97.3 |
|---|---|
| AAAA | 2a06:98c1:3120::3, 2a06:98c1:3121::3 |
| NS | austin.ns.cloudflare.com, melissa.ns.cloudflare.com |
| MX | _dc-mx.756ff4af013e.bdsmup.net (10) |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 188.114.96.3 answers for bdsmup.net at resolver 1.1.1.1:53.
IPv4 address 188.114.97.3 answers for bdsmup.net at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::3 answers for bdsmup.net at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::3 answers for bdsmup.net at resolver 1.1.1.1:53.
Mail exchanger _dc-mx.756ff4af013e.bdsmup.net has preference 10.
bdsmup.net is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.3 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for bdsmup.net is valid, with 63 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | bdsmup.net |
| Valid from | 4 October 2026 |
| Valid until | 2 January 2027 |
| Days left | 63 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.bdsmup.net, bdsmup.net.
Tech detection checked the fetched homepage and named 7 products. Source: wappalyzergo.
Apache HTTP Server is filed under Web servers.
Cloudflare is filed under CDN.
DataLife Engine is filed under CMS.
Google Analytics is filed under Analytics.
HTTP/3 is filed under Miscellaneous.
PHP is filed under Programming languages.
jQuery is filed under JavaScript libraries.
The homepage returned HTTP 200 in 160 ms. The target title is 31 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 160 ms |
| Title length | 31 yes |
| Quoted title | "Hot bdsm porn videos at BDSMup!" |
| Meta description | "Welcome to bdsmup.net - the biggest tube of ONLY hot bdsm porn videos. Hundreds of studios and categories. Bondage sex, bdsm blowjob, bbw bdsm and facesitting porn." yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | — |
| Canonical | https://bdsmup.net/ |
| Language | en-US |
| Links | 259 |
| Images | 16 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for bdsmup.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 bdsmup.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 0 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 5 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.
First checked on 30 October 2026; changes will appear here.
Cloudflare family DNS returned a block for bdsmup.net. That resolver covers adult and malware names.
bdsmup.net is placed in Toronto, Canada.
bdsmup.net expires on 8 April 2027 according to https://rdap.verisign.com/net/v1/domain/bdsmup.net.
The registry did not return a person or a company for bdsmup.net. RDAP often redacts the registrant. The registrar on file is Tucows Domains 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.