desikahani2.net

Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .

Online · 200SafeSSL: 78 days left7 years oldTranco #1693

One re-check per domain each UTC day.

85

desikahani2.net was registered on 13 Dec 2018 via Cloudflare, Inc. and the registry expiry is 13 Dec 2026. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/desikahani2.net.

desikahani2.net publishes 2 nameservers. DNSSEC is not signed.

desikahani2.net has 3 IPv4 addresses (104.26.12.146, 104.26.13.146, 172.67.73.254) and 3 IPv6 addresses (2606:4700:20::681a:c92, 2606:4700:20::681a:d92, 2606:4700:20::ac43:49fe). The geolocation database places 104.26.12.146 in Toronto, Canada.

The TLS certificate from WE1 is valid and has 78 days left (TLS 1.3). The homepage answered HTTP 200.

Tech detection named Cloudflare, HSTS, HTTP/3, MySQL, PHP, Redis, Redis Object Cache, WordPress, Yoast SEO and jQuery. The fingerprints ran on the homepage that was already downloaded.

No safety warning was recorded for desikahani2.net in the checks that ran.

Domain · RDAP/WHOIS

desikahani2.net was registered on 13 Dec 2018 via Cloudflare, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/net/v1/domain/desikahani2.net.

Registeredsince 13 Dec 2018
Created13 December 2018
Updated13 November 2025
Expires13 December 2026
RegistrarCloudflare, Inc.
Statusclient transfer prohibited
Nameserversjake.ns.cloudflare.com, lisa.ns.cloudflare.com
DNSSECno
Sourcehttps://rdap.verisign.com/net/v1/domain/desikahani2.net

desikahani2.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 jake.ns.cloudflare.com is published for desikahani2.net in the registration record from https://rdap.verisign.com/net/v1/domain/desikahani2.net.

Nameserver lisa.ns.cloudflare.com is published for desikahani2.net in the registration record from https://rdap.verisign.com/net/v1/domain/desikahani2.net.

DNS

desikahani2.net has 6 address records, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A104.26.12.146, 104.26.13.146, 172.67.73.254
AAAA2606:4700:20::681a:c92, 2606:4700:20::681a:d92, 2606:4700:20::ac43:49fe
NSjake.ns.cloudflare.com, lisa.ns.cloudflare.com
MXroute1.mx.cloudflare.net (4), route2.mx.cloudflare.net (58), route3.mx.cloudflare.net (71)
SPFpresent
DMARCabsent
CAAissue comodoca.com, issue digicert.com; cansignhttpexchanges=yes, issue letsencrypt.org, issue pki.goog; cansignhttpexchanges=yes, issue ssl.com, issuewild comodoca.com, issuewild digicert.com; cansignhttpexchanges=yes, issuewild letsencrypt.org, issuewild pki.goog; cansignhttpexchanges=yes, issuewild ssl.com
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

The SPF text record at desikahani2.net is "v=spf1 include:_spf.mx.cloudflare.net ~all".

IPv4 address 104.26.12.146 answers for desikahani2.net at resolver 1.1.1.1:53.

IPv4 address 104.26.13.146 answers for desikahani2.net at resolver 1.1.1.1:53.

IPv4 address 172.67.73.254 answers for desikahani2.net at resolver 1.1.1.1:53.

IPv6 address 2606:4700:20::681a:c92 answers for desikahani2.net at resolver 1.1.1.1:53.

IPv6 address 2606:4700:20::681a:d92 answers for desikahani2.net at resolver 1.1.1.1:53.

IPv6 address 2606:4700:20::ac43:49fe answers for desikahani2.net at resolver 1.1.1.1:53.

Mail exchanger route1.mx.cloudflare.net has preference 4.

Mail exchanger route2.mx.cloudflare.net has preference 58.

Mail exchanger route3.mx.cloudflare.net has preference 71.

Hosting and geo

desikahani2.net is placed in Toronto, Canada by the local geolocation database (db-ip).

Address104.26.12.146
CountryCanada
CityToronto
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for desikahani2.net is valid, with 78 days left and 2 subject alternative names. Source: tls:443.

IssuerWE1
Subjectdesikahani2.net
Valid from19 October 2026
Valid until17 January 2027
Days left78
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.desikahani2.net, desikahani2.net.

Tech stack

Tech detection checked the fetched homepage and named 10 products. Source: wappalyzergo.

  • Cloudflare · CDN
  • HSTS · Security
  • HTTP/3 · Miscellaneous
  • MySQL · Databases
  • PHP · Programming languages
  • Redis · Databases
  • Redis Object Cache · Caching
  • WordPress · CMS, Blogs
  • Yoast SEO · SEO, WordPress plugins
  • jQuery · JavaScript libraries

Cloudflare is filed under CDN.

HSTS is filed under Security.

HTTP/3 is filed under Miscellaneous.

MySQL is filed under Databases.

PHP is filed under Programming languages.

Redis is filed under Databases.

Redis Object Cache is filed under Caching.

WordPress is filed under CMS, Blogs.

Yoast SEO is filed under SEO, WordPress plugins.

jQuery is filed under JavaScript libraries.

On-page checks

The homepage returned HTTP 200 in 26 ms. The target title is 45 characters and the page has 1 H1 heading.

Status200
TTFB26 ms
Title length45 yes
Quoted title"Desi kahani - Indian Hindi desi sex stories -"
Meta description"Hindi me chudai ki kahaniya padhe desi kahani dot net par. Bhabhi, aunty, maa, behan ki Indian sex stories desi language me. -" yes
H1 count1
HSTSyes yes
CSPno
X-Frame-OptionsSAMEORIGIN
Robots metaindex, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
Canonicalhttps://www.desikahani2.net/
Languageen-US
Links452
Images1
Faviconyes

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 desikahani2.net is clear, and URLhaus is clear. Source: family DNS and local lists.

Family DNSclear
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSyes
CSPno

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 10 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

First checked on 30 October 2026; changes will appear here.

Questions

Is desikahani2.net 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 desikahani2.net?

desikahani2.net is placed in Toronto, Canada.

When does desikahani2.net expire?

desikahani2.net expires on 13 December 2026 according to https://rdap.verisign.com/net/v1/domain/desikahani2.net.

Who owns desikahani2.net?

The registry did not return a person or a company for desikahani2.net. RDAP often redacts the registrant. The registrar on file is Cloudflare, Inc..

Sources

  • RDAP source https://rdap.verisign.com/net/v1/domain/desikahani2.net at 2026-10-30T14:51:33Z
  • DNS source 1.1.1.1:53 at 2026-10-30T14:51:33Z
  • TLS source tls:443 at 2026-10-30T14:51:33Z
  • HTTP source https://desikahani2.net/ at 2026-10-30T14:51:33Z
  • Tech source wappalyzergo at 2026-10-30T14:51:33Z
  • Geo source db-ip at 2026-10-30T14:51:33Z
  • Safety source family DNS and local lists at 2026-10-30T14:51:33Z

Methodology

Related reports

No other indexable reports share this TLD, host, or registrar yet.

.net Cloudflare, Inc.

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.

Removal policy

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.