Skip to main content

Security report for jetdate.in

JetDate · Other · India

Medium risk. 5 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

73/100

Risk levelMedium

0–100, higher is better. How it is calculated

JetDate is an adult escort advertising platform primarily serving Indian cities, offering listings for female, male, and shemale escorts. The website provides a straightforward service allowing adult providers to advertise their companionship services and users to find escorts. The business model is focused on advertising and listing services without direct booking or payment facilitation. The platform targets adult users seeking escort services and positions itself as a niche player in the Indian adult services market. Technically, the website uses modern frontend technologies including JavaScript, CSS with Bootstrap styling, and integrates Google Analytics for visitor tracking. The site is mobile-optimized with responsive design and loads with moderate performance. HTTPS is enforced, ensuring secure communication. However, there is no evidence of a CMS or advanced hosting details. SEO and accessibility are basic but adequate for the site's purpose. From a security perspective, the site uses HTTPS but lacks advanced security headers and publicly available security or incident response policies. No vulnerabilities or exposed sensitive data were detected in the HTML content. Privacy compliance is basic; while privacy and cookie policies exist, there is no explicit cookie consent mechanism, which is a compliance gap especially under GDPR. No company contact information or certifications were found, which limits business credibility. Overall, JetDate presents a functional and niche adult advertising platform with moderate technical maturity and security posture. Strategic improvements in privacy compliance, security policy transparency, and contact information disclosure would enhance trust and compliance. The site is accessible without WAF or blocking mechanisms, allowing full content analysis.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

5 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…
  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  3. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

Need hands-on remediation? Email guard@offseq.com

Keep watching jetdate.in

This scan found 19 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. The full timeline opens with your unlock code.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
75
Security headers
55
Email security
75
DNS health
80
Network security
100
GDPR outside view
53
Average
73

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

JetDate operates in the adult services advertising sector, focusing on escort listings in India. Its competitive advantage lies in providing a free basic listing service for individual escorts and agencies, targeting adult users seeking companionship. The business model is advertising-based without direct transaction handling, reducing regulatory complexity. The platform supports multiple languages, indicating an intent to serve diverse Indian linguistic groups. Growth potential exists in expanding city coverage and service categories. The partnership ecosystem is not evident from the data, and no parent or subsidiary companies are identified. Revenue streams likely derive from premium listings or advertising fees. The platform maintains a moderate market position within its niche, with trust signals such as terms of use and anti-human trafficking links enhancing credibility.

Security posture

The website enforces HTTPS, which is a fundamental security measure. However, it lacks visible security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options, which are recommended to mitigate common web attacks. No incident response or security policy information is publicly available, indicating limited transparency in security governance. The absence of a vulnerability disclosure or security.txt file further limits security communication. Forms on the site appear basic with no advanced security controls visible. Google Analytics is used for tracking, but no cookie consent mechanism is implemented, posing privacy compliance risks. Overall, the security maturity is moderate but could be improved by adopting best practices and enhancing transparency.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against common web vulnerabilities.
  2. Publish a clear security policy and incident response plan on the website to improve transparency and user trust.
  3. Add a cookie consent banner/mechanism to comply with GDPR and other privacy regulations.
  4. Provide verified company contact information to improve business credibility and user confidence.
  5. Consider implementing a vulnerability disclosure policy or security.txt file to facilitate responsible security reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
JetDate
Description
JetDate is a platform where adult providers can advertise their services and users can get in touch. It focuses on escort listings including female, male, and shemale escorts, primarily in Indian cities.
Key services
Escort listings, Advertising escort services
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, CSS, FontAwesome, Google Analytics (gtag.js)
Frameworks
Bootstrap (CSS classes suggest)
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics (gtag.js)
Tracking level
moderate
Privacy practices
basic

Advertising

Transparency
basic

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
moderate

Key observations

  1. Website is an adult escort advertising platform targeting Indian cities.
  2. Content is accessible and not blocked by WAF or security challenges.
  3. No direct company contact emails or phone numbers found.
  4. Privacy and cookie policies exist but lack explicit consent mechanisms.
  5. No visible security policy or incident response information.
  6. Uses Google Analytics for tracking without explicit cookie consent banner.
  7. No visible certifications or security disclosures.
  8. Site uses HTTPS and modern frontend technologies with responsive design.
Technical notes

Notes

The website uses a modern frontend stack with JavaScript, CSS (Bootstrap), and FontAwesome icons. Google Analytics is integrated for visitor tracking. The site is mobile responsive and uses HTTPS for secure communication. Performance is moderate with deferred script loading and CSS preloading techniques. No CMS or backend technologies are explicitly identified. The site lacks advanced accessibility features but maintains basic usability standards. SEO is supported by meta tags and canonical links. Hosting provider details are not disclosed. Technical debt appears low but could be improved by adding security headers and privacy compliance mechanisms.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with jetdate.in. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review jetdate.in.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.