Is vplink.in safe to use as a vendor?

vplink.in scored 65/100 on LynxRadar's security posture assessment. The domain partially meets security requirements with some gaps to address. 5 checks passed, 8 warnings, 2 critical issues across 16 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does vplink.in use?

vplink.in uses TLSv1.3 with TLS_AES_256_GCM_SHA384. TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.

Does vplink.in have SPF configured?

Yes. SPF record: v=spf1 ip4:82.25.97.148 ip4:216.137.180.102 +a +mx ~all

Does vplink.in have security headers configured?

vplink.in has 2 of 5 recommended security headers. Present: X-Content-Type-Options, X-Frame-Options. Missing: CSP, Referrer-Policy, Permissions-Policy.

Has vplink.in been involved in a data breach?

No known breaches found. No known breaches found in public disclosure databases.

Does vplink.in have known CVE vulnerabilities?

Detected technologies: cloudflare. (cloudflare detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.

vplink.in Security Report — Grade D (65/100)

Q: Does vplink.in have DMARC configured?

Yes. vplink.in's DMARC policy is set to 'none'. SPF record: yes. Strengths: DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 2/10 (within limit). Issues: DMARC policy is 'none' (monitoring only, no enforcement). Note: DKIM couldn't be confirmed from outside (custom selector names can't be looked up, and some DNS hosts don't expose them), so it isn't counted against the score.

Q: Does vplink.in use HSTS?

No. Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks. If this domain is in the browser HSTS preload list, browsers may still enforce HTTPS — but the header should be present for full coverage.

Q: Is vplink.in's SSL certificate valid?

Issues detected. Strengths: Certificate valid, 49 days remaining; Issued by Google Trust Services; 240 certificates logged in CT. Issues: Certificates issued by 7 different CAs (threshold: 5 for 240 logged certs) — possible misconfiguration or shadow IT. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.

Q: Does vplink.in have DNSSEC enabled?

No. Strengths: 2 nameservers configured (collins.ns.cloudflare.com, ed.ns.cloudflare.com); SOA record present and MNAME consistent with NS set; 1 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 3 A record(s), 3 AAAA record(s). Issues: All nameservers are from a single provider (cloudflare.com) — a provider outage takes down the domain; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).

Trust rating

Weak · 65/100

Procurement snapshot

0 critical findings identified — these point to architectural gaps, not just configuration tweaks.

Strengths

TLS Configuration

TLS Protocol Support

Known Breaches

CVE Exposure

Questions to ask

Confirm backup mail server configuration

Estimated remediation effort: 2–5 days

Based on a passive external scan — supplement with vendor-provided attestations, not a replacement.

Trust Score Trend

→ No change 1 scan · Last scanned October 15, 2026

Score

100 75 50 25 0

vplink.in

65/100

Compliance & Certifications

Not yet verified

SOC 2 Type II

Audit report not on file

3rd party · AICPA

ISO 27001

Certificate not on file

3rd party · accredited body

GDPR

DPA not on file

Self-reported

CCPA

Self-reported

Incident History

No public breaches on record

Security Posture

10 items need attention

5 passed

Finish setting up email authentication

DMARC / Email Security

2–4 hours High

Spoofed emails can still reach your customers and partners until this is fully enforced. Email authentication for vplink.in is partly set up, but there are gaps: your DMARC policy is set to monitor-only, so nothing actually gets blocked yet. Until it's fully in place, someone could still send a convincing fake email pretending to be you.

NIST SP 800-177r1§4

Trustworthy Email recommends SPF, DKIM and DMARC for every email domain

How to fix this

1Change your DMARC policy from "none" to "quarantine" in your domain's DNS settings (check with whoever manages your website or domain registration) — this moves suspicious mail to spam instead of just watching it happen. Your current record with just that change:

v=DMARC1; p=quarantine; rua=mailto:[email protected]

2If DKIM signing isn't on yet (we can't confirm it from outside): Turn on DKIM signing — look for "DKIM" under your email provider's admin/security settings. It gives you a record to add in your domain's DNS settings (check with whoever manages your website or domain registration).

3Double-check it's live: search "dmarc record checker" and enter vplink.in.

Email authentication guide

Report unlocked.

View all 5 passed checks

TLS Configuration

TLS Protocol Support

Known Breaches

CVE Exposure

Subprocessors & Tech Stack

Couldn't check: Malware / Phishing Blocklist — the check didn't complete (the site blocked or timed out our scanner, or a data source was unavailable), so this isn't counted in the score.

Company Signals

Operational risk

Last funding

Employees

Trust Resources

Claim profile →

Trust Center

Not detected

DPA (Data Processing Agreement)

Subprocessors List

Similar companies

Appears in

Vendors graded D

837 companies · LynxRadar ranking

Blocking Issues

Not enabled

Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks. If this domain is in the browser HSTS preload list, browsers may still enforce HTTPS — but the header should be present for full coverage.

Likelihood: ★★★☆☆

Impact: ★★★★☆

2/5 present

Missing: CSP, Referrer-Policy, Permissions-Policy

Likelihood: ★★★☆☆

Impact: ★★★☆☆

High Priority

p=none

Strengths: DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 2/10 (within limit). Issues: DMARC policy is 'none' (monitoring only, no enforcement). Note: DKIM couldn't be confirmed from outside (custom selector names can't be looked up, and some DNS hosts don't expose them), so it isn't counted against the score.

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Medium Priority

Warn

Strengths: Mail handled by mail.vplink.in; 1 MX record(s) configured. Issues: Only 1 MX record — no failover if primary mail server is unavailable.

Likelihood: ★★☆☆☆

Impact: ★★☆☆☆

Warn

Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks; sending servers cannot verify your mail server requires TLS; No TLSRPT record (_smtp._tls) — TLS delivery failures won't be reported to the domain owner.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Not enabled

Strengths: 2 nameservers configured (collins.ns.cloudflare.com, ed.ns.cloudflare.com); SOA record present and MNAME consistent with NS set; 1 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 3 A record(s), 3 AAAA record(s). Issues: All nameservers are from a single provider (cloudflare.com) — a provider outage takes down the domain; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Warn

Strengths: 2 cookie(s) analyzed; All cookies have Secure flag; All cookies have HttpOnly flag. Issues: 2/2 cookie(s) missing SameSite attribute (AppSession, csrfToken).

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Best Practice

Warn

No CAA records found in the DNS tree for this domain. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorised CAs only, reducing the risk of misissued certificates.

Likelihood: ★☆☆☆☆

Impact: ★☆☆☆☆

Warn

No security.txt found. Publishing a security.txt at /.well-known/security.txt is the industry standard (RFC 9116) for vulnerability disclosure policies. Its absence may indicate a less mature security program.

Likelihood: ★☆☆☆☆

Impact: ★☆☆☆☆

Issues

Strengths: Certificate valid, 49 days remaining; Issued by Google Trust Services; 240 certificates logged in CT. Issues: Certificates issued by 7 different CAs (threshold: 5 for 240 logged certs) — possible misconfiguration or shadow IT. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.

Likelihood: ★★☆☆☆

Impact: ★★☆☆☆