tamilscandals2.com

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

Online · 200Family DNS blockedSSL: 80 days left4 years old

One re-check per domain each UTC day.

65

tamilscandals2.com was registered on 2 May 2022 via Cloudflare, Inc. and the registry expiry is 2 May 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/tamilscandals2.com.

tamilscandals2.com publishes 2 nameservers. DNSSEC is signed.

tamilscandals2.com has 2 IPv4 addresses (188.114.96.3, 188.114.97.3) and 2 IPv6 addresses (2a06:98c1:3120::4, 2a06:98c1:3121::4). The geolocation database places 188.114.96.3 in Toronto, Canada.

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

Tech detection named Bootstrap, Cloudflare, Contact Form 7, Infinite Scroll, Lightbox, MySQL, PHP, Redis, Redis Object Cache, WordPress, Yoast SEO, cdnjs, imagesLoaded, jQuery, jQuery Migrate and jsDelivr. The fingerprints ran on the homepage that was already downloaded.

Domain · RDAP/WHOIS

tamilscandals2.com was registered on 2 May 2022 via Cloudflare, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/tamilscandals2.com.

Registeredsince 2 May 2022
Created2 May 2022
Updated2 April 2026
Expires2 May 2027
RegistrarCloudflare, Inc.
Statusclient transfer prohibited
Nameserversjake.ns.cloudflare.com, lisa.ns.cloudflare.com
DNSSECyes
Sourcehttps://rdap.verisign.com/com/v1/domain/tamilscandals2.com

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

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

DNS

tamilscandals2.com has 4 address records, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A188.114.96.3, 188.114.97.3
AAAA2a06:98c1:3120::4, 2a06:98c1:3121::4
NSjake.ns.cloudflare.com, lisa.ns.cloudflare.com
MXroute3.mx.cloudflare.net (50), route1.mx.cloudflare.net (76), route2.mx.cloudflare.net (100)
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
DNSSECsigned
Resolver1.1.1.1:53

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

IPv4 address 188.114.96.3 answers for tamilscandals2.com at resolver 1.1.1.1:53.

IPv4 address 188.114.97.3 answers for tamilscandals2.com at resolver 1.1.1.1:53.

IPv6 address 2a06:98c1:3120::4 answers for tamilscandals2.com at resolver 1.1.1.1:53.

IPv6 address 2a06:98c1:3121::4 answers for tamilscandals2.com at resolver 1.1.1.1:53.

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

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

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

Hosting and geo

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

Address188.114.96.3
CountryCanada
CityToronto
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for tamilscandals2.com is valid, with 80 days left and 2 subject alternative names. Source: tls:443.

IssuerWE1
Subjecttamilscandals2.com
Valid from21 October 2026
Valid until19 January 2027
Days left80
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.tamilscandals2.com, tamilscandals2.com.

Tech stack

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

  • Bootstrap · UI frameworks
  • Cloudflare · CDN
  • Contact Form 7 · WordPress plugins, Form builders
  • Infinite Scroll · JavaScript libraries
  • Lightbox · JavaScript libraries
  • MySQL · Databases
  • PHP · Programming languages
  • Redis · Databases
  • Redis Object Cache · Caching
  • WordPress · CMS, Blogs
  • Yoast SEO · SEO, WordPress plugins
  • cdnjs · CDN
  • imagesLoaded · JavaScript libraries
  • jQuery · JavaScript libraries
  • jQuery Migrate · JavaScript libraries
  • jsDelivr · CDN

Bootstrap is filed under UI frameworks.

Cloudflare is filed under CDN.

Contact Form 7 is filed under WordPress plugins, Form builders.

Infinite Scroll is filed under JavaScript libraries.

Lightbox is filed under JavaScript libraries.

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.

cdnjs is filed under CDN.

imagesLoaded is filed under JavaScript libraries.

jQuery is filed under JavaScript libraries.

jQuery Migrate is filed under JavaScript libraries.

jsDelivr is filed under CDN.

On-page checks

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

Status200
TTFB33 ms
Title length73 no
Quoted title"Tamil Scandals - தமிழ் காம கதைகள் | தமிழ் ஆபாச வீடியோ | தமிழ் செக்ஸ் படம்"
Meta description"இலவச சவுத் இந்தியன் தமிழ் செக்ஸ் தளம் ❤️ Tamil Sex Stories ❤️ Tamil Sex Photos ❤️Tamil Sex Videos ❤️Tamil Kamathaikal❤️ தினமும் பதிவு செய்யப்படும்" yes
H1 count1
HSTSno no
CSPno
X-Frame-Options—
Robots metaindex, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
Canonicalhttps://www.tamilscandalsx.com/
Languageen-US
Links281
Images22
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 tamilscandals2.com is blocked, and URLhaus is clear. Source: family DNS and local lists.

Family DNSblocked
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSno
CSPno

Cloudflare family DNS returned a block for tamilscandals2.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 15 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 tamilscandals2.com safe?

Cloudflare family DNS returned a block for tamilscandals2.com. That resolver covers adult and malware names.

Who hosts tamilscandals2.com?

tamilscandals2.com is placed in Toronto, Canada.

When does tamilscandals2.com expire?

tamilscandals2.com expires on 2 May 2027 according to https://rdap.verisign.com/com/v1/domain/tamilscandals2.com.

Who owns tamilscandals2.com?

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

Sources

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

Methodology

Related reports

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

.com 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.