sexbaba.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 65 days left12 years old
60
sexbaba.net was registered on 5 Dec 2013 via TuringSign Inc. d/b/a Cosmotown and the registry expiry is 5 Dec 2026. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/sexbaba.net.
sexbaba.net publishes 2 nameservers. DNSSEC is not signed.
sexbaba.net has 2 IPv4 addresses (104.21.51.207, 172.67.185.227) and 2 IPv6 addresses (2606:4700:3031::ac43:b9e3, 2606:4700:3033::6815:33cf). The geolocation database places 104.21.51.207 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 65 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, HTTP/3, MySQL, PHP and XenForo. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
sexbaba.net was registered on 5 Dec 2013 via TuringSign Inc. d/b/a Cosmotown. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/net/v1/domain/sexbaba.net.
| Registered | since 5 Dec 2013 |
|---|---|
| Created | 5 December 2013 |
| Updated | 2 December 2025 |
| Expires | 5 December 2026 |
| Registrar | TuringSign Inc. d/b/a Cosmotown |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | alex.ns.cloudflare.com, elsa.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/sexbaba.net |
sexbaba.net 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.
sexbaba.net 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.
sexbaba.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.
sexbaba.net 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 alex.ns.cloudflare.com is published for sexbaba.net in the registration record from https://rdap.verisign.com/net/v1/domain/sexbaba.net.
Nameserver elsa.ns.cloudflare.com is published for sexbaba.net in the registration record from https://rdap.verisign.com/net/v1/domain/sexbaba.net.
DNS
sexbaba.net has 4 address records, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.51.207, 172.67.185.227 |
|---|---|
| AAAA | 2606:4700:3031::ac43:b9e3, 2606:4700:3033::6815:33cf |
| NS | alex.ns.cloudflare.com, elsa.ns.cloudflare.com |
| MX | route1.mx.cloudflare.net (20), route3.mx.cloudflare.net (64), route2.mx.cloudflare.net (72) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at sexbaba.net is "v=spf1 include:_spf.mx.cloudflare.net ~all".
IPv4 address 104.21.51.207 answers for sexbaba.net at resolver 1.1.1.1:53.
IPv4 address 172.67.185.227 answers for sexbaba.net at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3031::ac43:b9e3 answers for sexbaba.net at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3033::6815:33cf answers for sexbaba.net at resolver 1.1.1.1:53.
Mail exchanger route1.mx.cloudflare.net has preference 20.
Mail exchanger route3.mx.cloudflare.net has preference 64.
Mail exchanger route2.mx.cloudflare.net has preference 72.
Hosting and geo
sexbaba.net is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.51.207 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for sexbaba.net is valid, with 65 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | sexbaba.net |
| Valid from | 6 October 2026 |
| Valid until | 4 January 2027 |
| Days left | 65 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.sexbaba.net, sexbaba.net.
Tech stack
Tech detection checked the fetched homepage and named 5 products. Source: wappalyzergo.
- Cloudflare · CDN
- HTTP/3 · Miscellaneous
- MySQL · Databases
- PHP · Programming languages
- XenForo · Message boards
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
MySQL is filed under Databases.
PHP is filed under Programming languages.
XenForo is filed under Message boards.
On-page checks
The homepage returned HTTP 200 in 56 ms. The target title is 27 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 56 ms |
| Title length | 27 yes |
| Quoted title | "Sex Baba Indian Adult Forum" |
| Meta description | "🌶️Explore Sex Baba Forum for Bollywood & South actress nudes & hot Hindi sex stories. Join our community for your wildest fantasies.😈" yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | — |
| Canonical | https://sexbaba.co/ |
| Language | en-US |
| Links | 98 |
| Images | 9 |
| 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 sexbaba.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 sexbaba.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.
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 5 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.
Change history
First checked on 30 October 2026; changes will appear here.
Questions
Is sexbaba.net safe?
Cloudflare family DNS returned a block for sexbaba.net. That resolver covers adult and malware names.
Who hosts sexbaba.net?
sexbaba.net is placed in Toronto, Canada.
When does sexbaba.net expire?
sexbaba.net expires on 5 December 2026 according to https://rdap.verisign.com/net/v1/domain/sexbaba.net.
Who owns sexbaba.net?
The registry did not return a person or a company for sexbaba.net. RDAP often redacts the registrant. The registrar on file is TuringSign Inc. d/b/a Cosmotown.
Sources
- RDAP source https://rdap.verisign.com/net/v1/domain/sexbaba.net at 2026-10-30T14:55:31Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:55:31Z
- TLS source tls:443 at 2026-10-30T14:55:31Z
- HTTP source https://sexbaba.net/ at 2026-10-30T14:55:31Z
- Tech source wappalyzergo at 2026-10-30T14:55:31Z
- Geo source db-ip at 2026-10-30T14:55:31Z
- Safety source family DNS and local lists at 2026-10-30T14:55:31Z
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.