vfrsdk.com security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

84risk

Critical

Exposed services or known CVEs need attention now.

0Critical

3High

10Medium

6Low

1Info

Collected 9 hours ago11.8sfrom cache

Certificate Transparency4
DNS resolution3
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs9
Registration
DNS posture4
Email authentication0
Certificate
Security headers0
Archived URLs
Analysis20

noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.

Shodan matched these CVEs against the service banners it saw on 204.168.202.226 (config.vfrsdk.com), which advertise openssh 9.6p1, nginx 1.24.0. These are version-fingerprint matches, not confirmed exploits: a distribution may have back-ported the fix while leaving the banner unchanged. Severity reflects the volume of known issues associated with this host, not a CVSS score. CVE-2025-23419 CVE-2023-44487
What to do
Confirm the running versions on 204.168.202.226 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2025-23419 ↗CVE-2023-44487 ↗
asset: 204.168.202.226
Shodan matched these CVEs against the service banners it saw on 77.42.84.185 (vfrsdk.com), which advertise openssh 9.6p1, nginx 1.24.0. These are version-fingerprint matches, not confirmed exploits: a distribution may have back-ported the fix while leaving the banner unchanged. Severity reflects the volume of known issues associated with this host, not a CVSS score. CVE-2025-23419 CVE-2023-44487
What to do
Confirm the running versions on 77.42.84.185 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2025-23419 ↗CVE-2023-44487 ↗
asset: 77.42.84.185
SPF and DKIM alone do not protect the From: address a person sees. Without DMARC, a spoofed message can pass SPF for some other domain and still display yours.
What to do
Publish `_dmarc.vfrsdk.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@vfrsdk.com"`, review the reports, then move to p=quarantine and p=reject.
asset: vfrsdk.com
204.168.202.226 (config.vfrsdk.com) reports openssh 9.6p1, nginx 1.24.0. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 204.168.202.226
Public SSH invites credential stuffing and key brute force.
What to do
Restrict 22/tcp to a VPN, bastion, or allow-listed source range.
asset: 204.168.202.226:22
77.42.84.185 (vfrsdk.com) reports openssh 9.6p1, nginx 1.24.0. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 77.42.84.185
Public SSH invites credential stuffing and key brute force.
What to do
Restrict 22/tcp to a VPN, bastion, or allow-listed source range.
asset: 77.42.84.185:22
Public SSH invites credential stuffing and key brute force.
What to do
Restrict 22/tcp to a VPN, bastion, or allow-listed source range.
asset: 77.42.93.251:22
Without HSTS the browser will still try http:// first on a fresh visit, which is the window an on-path attacker uses.
What to do
Send `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you are sure everything works over HTTPS.
asset: https://vfrsdk.com/
CSP is the main defence that limits what an injected script can do. Without it, any XSS bug is fully exploitable.
What to do
Start with a report-only policy, tighten it against the reports, then enforce.
asset: https://vfrsdk.com/
No X-Frame-Options or CSP frame-ancestors directive, so another site can load this page invisibly inside its own and trick users into clicking.
What to do
Send `X-Frame-Options: DENY` or `Content-Security-Policy: frame-ancestors ’none’`.
asset: https://vfrsdk.com/
Nothing tells receiving mail servers which hosts may send as @vfrsdk.com, so anyone can. Even a domain that sends no mail should say so, or it becomes a free spoofing target.
What to do
Publish `v=spf1 -all` to state that this domain sends no mail.
asset: vfrsdk.com
Without clientTransferProhibited, a compromised registrar account can move the domain to another registrar in days, with no second step.
What to do
Enable the transfer lock (and registrar lock, if offered) in the registrar control panel.
asset: vfrsdk.com
77.42.93.251 (demo.vfrsdk.com) reports openssh 9.6p1. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 77.42.93.251
qa.vfrsdk.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: qa.vfrsdk.com
demo.vfrsdk.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: demo.vfrsdk.com
Lets browsers guess content types, which turns some upload and text endpoints into script injection points.
What to do
Send `X-Content-Type-Options: nosniff` on every response.
asset: https://vfrsdk.com/
Full URLs — including any tokens or IDs in them — are sent to every third party the page links to.
What to do
Send `Referrer-Policy: strict-origin-when-cross-origin`.
asset: https://vfrsdk.com/
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: vfrsdk.com
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: vfrsdk.com

final https://vfrsdk.com/status 200time 706msstack cloudflare · Express

✓http:// redirects to https://
✗Strict-Transport-Security
✗Content-Security-Policy
✗Clickjacking protection
✗X-Content-Type-Options
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

–No MX records — domain does not receive mail
✗SPF
no record
✗DMARC
no record
–MTA-STSn/a

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
ns-1496.awsdns-59.org ns-1965.awsdns-53.co.uk ns-275.awsdns-34.com ns-747.awsdns-29.net

✓Registered with Amazon Registrar, Inc.3.6 years old
vfrsdk.com
✓Registration expiry153 days
2027-02-07
✗Transfer lock
none
✓4 nameservers at registry
ns-1496.awsdns-59.org ns-1965.awsdns-53.co.uk ns-275.awsdns-34.com ns-747.awsdns-29.net

Address	Ports	CVEs	Edge	Network
204.168.202.226 config.vfrsdk.com +1	22804438080	2	direct	—
77.42.84.185 vfrsdk.com +1	22808080	2	direct	—
77.42.93.251 demo.vfrsdk.com +1	228080	0	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

vfrsdk.com security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames