wildsexting.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 72 days left11 years oldTranco #363298
70
wildsexting.com was registered on 29 Dec 2014 via Dynadot Inc and the registry expiry is 29 Dec 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/wildsexting.com.
wildsexting.com publishes 2 nameservers. DNSSEC is not signed.
wildsexting.com 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 72 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Discourse, HTTP/3 and Ruby on Rails. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
wildsexting.com was registered on 29 Dec 2014 via Dynadot Inc. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/wildsexting.com.
| Registered | since 29 Dec 2014 |
|---|---|
| Created | 29 December 2014 |
| Updated | 27 March 2026 |
| Expires | 29 December 2027 |
| Registrar | Dynadot Inc |
| Status | client transfer prohibited |
| Nameservers | lamar.ns.cloudflare.com, virginia.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/wildsexting.com |
wildsexting.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.
Nameserver lamar.ns.cloudflare.com is published for wildsexting.com in the registration record from https://rdap.verisign.com/com/v1/domain/wildsexting.com.
Nameserver virginia.ns.cloudflare.com is published for wildsexting.com in the registration record from https://rdap.verisign.com/com/v1/domain/wildsexting.com.
DNS
wildsexting.com 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 | lamar.ns.cloudflare.com, virginia.ns.cloudflare.com |
| MX | mx.yandex.net (10) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at wildsexting.com is "v=spf1 redirect=_spf.yandex.net".
The DMARC text record at _dmarc.wildsexting.com is "v=DMARC1; p=reject; sp=reject; rua=mailto:[email protected]; ruf=mailto:[email protected]; adkim=r; aspf=r; fo=1".
IPv4 address 188.114.96.3 answers for wildsexting.com at resolver 1.1.1.1:53.
IPv4 address 188.114.97.3 answers for wildsexting.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::3 answers for wildsexting.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::3 answers for wildsexting.com at resolver 1.1.1.1:53.
Mail exchanger mx.yandex.net has preference 10.
Hosting and geo
wildsexting.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.3 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for wildsexting.com is valid, with 72 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | wildsexting.com |
| Valid from | 14 October 2026 |
| Valid until | 12 January 2027 |
| Days left | 72 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.wildsexting.com, wildsexting.com.
Tech stack
Tech detection checked the fetched homepage and named 4 products. Source: wappalyzergo.
- Cloudflare · CDN
- Discourse · Message boards
- HTTP/3 · Miscellaneous
- Ruby on Rails · Web frameworks
Cloudflare is filed under CDN.
Discourse is filed under Message boards.
HTTP/3 is filed under Miscellaneous.
Ruby on Rails is filed under Web frameworks.
On-page checks
The homepage returned HTTP 200 in 30 ms. The target title is 70 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 30 ms |
| Title length | 70 no |
| Quoted title | "WildSexting💋 - Sexting on Telegram, WhatsApp, Kik, Discord, Zangi etc." |
| Meta description | "HOT sexting partners (girls, guys, trans & groups) on Telegram, WhatsApp, Kik, Discord, Zangi, OnlyFans, Signal, Zoom, Instagram, TikTok, Twitter, Facebook & More!" yes |
| H1 count | 0 |
| HSTS | no no |
| CSP | yes |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | — |
| Canonical | https://www.wildsexting.com/ |
| Language | en |
| Links | 162 |
| Images | 30 |
| 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 wildsexting.com 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 | yes |
Cloudflare family DNS returned a block for wildsexting.com. 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 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 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
- October 2026: dns aaaa changed from 2a06:98c1:3120::4,2a06:98c1:3121::4 to 2a06:98c1:3120::3,2a06:98c1:3121::3.
Questions
Is wildsexting.com safe?
Cloudflare family DNS returned a block for wildsexting.com. That resolver covers adult and malware names.
Who hosts wildsexting.com?
wildsexting.com is placed in Toronto, Canada.
When does wildsexting.com expire?
wildsexting.com expires on 29 December 2027 according to https://rdap.verisign.com/com/v1/domain/wildsexting.com.
Who owns wildsexting.com?
The registry did not return a person or a company for wildsexting.com. RDAP often redacts the registrant. The registrar on file is Dynadot Inc.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/wildsexting.com at 2026-10-30T14:20:07Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:20:07Z
- TLS source tls:443 at 2026-10-30T14:20:07Z
- HTTP source https://wildsexting.com/ at 2026-10-30T14:20:07Z
- Tech source wappalyzergo at 2026-10-30T14:20:07Z
- Geo source db-ip at 2026-10-30T14:20:07Z
- Safety source family DNS and local lists at 2026-10-30T14:20:07Z
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.