FairSRS Score 78/100 · Grade C · last scanned Aug 13, 2026
Powered by Shodan, tuned by FairTPRM!
Scanning external signals… this can take up to a couple of minutes.
78/100 FairSRS Score | C Grade | Needs Improvement Signal Rating | 24 positive signals 9 risk signals 41 host(s), 52 subdomain(s) |
Categories with items of opportunity are clickable - open one to see the action items that would raise its score.
| 77/100 | ||
| 81/100 | ||
| 74/100 | ||
| Vulnerability Exposure | 95/100 | |
| 56/100 |
11 items of opportunity in this category: 6 risk signals costing -3 points, and 5 strengths to extend to more hosts worth up to +18 points.
Deprecated TLS 1.0 is still enabled
| TLS Versions | TLSv1, -SSLv2, -SSLv3, TLSv1.1, TLSv1.2, -TLSv1.3 |
|---|---|
| Adoption | 3 of 35 SSL hosts (9%) |
Deprecated TLS 1.1 is still enabled
| TLS Versions | TLSv1, -SSLv2, -SSLv3, TLSv1.1, TLSv1.2, -TLSv1.3 |
|---|---|
| Adoption | 3 of 35 SSL hosts (9%) |
SSL/TLS certificate has expired
| Certificate Issuer | Plesk |
|---|---|
| Subject | Plesk |
| Expired | 2022-12-07T04:02:54 |
| Adoption | 1 of 35 SSL hosts (3%) |
Critically insecure SSL protocols are enabled
| TLS Versions | TLSv1, -SSLv2, SSLv3, TLSv1.1, TLSv1.2, -TLSv1.3 |
|---|---|
| Adoption | 1 of 35 SSL hosts (3%) |
Certificate is self-signed (not issued by a trusted CA)
| Issuer (O) | AZIA Co.,Ltd. |
|---|---|
| Subject (O) | AZIA Co.,Ltd. |
| Issuer (CN) | wcasp3-fanclwww.webcas.net |
| Subject (CN) | wcasp3-fanclwww.webcas.net |
| Adoption | 2 of 35 SSL hosts (6%) |
Domain not found in certificate Subject Alternative Names
| Certificate CN | wcasp3-fanclwww.webcas.net |
|---|---|
| Certificate SANs | (none) |
| Expected Domain | m.fancl.co.jp |
| Adoption | 4 of 35 SSL hosts (11%) |
You already do these right on some hosts - rolling them out to the rest is the fastest way to raise this score. Points shown are the signal’s full value; the actual gain scales with how many hosts you cover.
Present on of 35 hosts (29%).
Present on of 35 hosts (11%).
Present on of 35 hosts (9%).
Present on of 35 hosts (74%).
Present on of 35 hosts (83%).
2 items of opportunity in this category: 1 strength to extend to more hosts worth up to +7 points, and 1 unearned strength worth up to +7 points.
You already do these right on some hosts - rolling them out to the rest is the fastest way to raise this score. Points shown are the signal’s full value; the actual gain scales with how many hosts you cover.
Present on of 37 hosts (51%).
Signals this category has on no host yet. Points are the signal’s full value - the effect on the overall score is weighted.
7 items of opportunity in this category: 1 risk signal costing -1 points, and 6 strengths to extend to more hosts worth up to +22 points.
Server header reveals software version information
| Server Header | apache/2.4.37 (ubuntu) |
|---|---|
| Adoption | 3 of 37 HTTP hosts (8%) |
You already do these right on some hosts - rolling them out to the rest is the fastest way to raise this score. Points shown are the signal’s full value; the actual gain scales with how many hosts you cover.
Present on of 37 hosts (8%).
Present on of 37 hosts (14%).
Present on of 37 hosts (24%).
Present on of 37 hosts (16%).
Present on 1 of 37 hosts (3%).
Present on 34 of 37 hosts (92%).
Re-scan to list the 3 hosts still missing this.
6 items of opportunity in this category: 2 risk signals costing -14 points, and 4 unearned strengths worth up to +35 points.
SMTP port 25 is open -- potential for email relay abuse
| Port | 25 |
|---|---|
| Host | 101.110.14.193 |
| SMTP Banner | 220 wcasp3-fanclwww ESMTP Postfix 250-wcasp3-fanclwww 250-PIPELINING 250-SIZE 10240000 250-ETRN 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN |
SPF record uses soft fail (~all) instead of hard fail (-all) -- mail servers may still accept spoofed email
| SPF Record | v=spf1 include:spf.protection.outlook.com include:u6577238.wl239.sendgrid.net include:mdhaiti.maildealer.jp include:webcas.net include:spf.securemx.jp ip4:13.71.133.58 ~all |
|---|
Signals this category has on no host yet. Points are the signal’s full value - the effect on the overall score is weighted.
| Category | Signal | Points |
|---|---|---|
| Email Security | Open SMTP (Port 25) SMTP port 25 is open -- potential for email relay abuse m.fancl.co.jp 101.110.14.193 :25 | -8 |
| Email Security | SPF Soft Fail (~all) SPF record uses soft fail (~all) instead of hard fail (-all) -- mail servers may still accept spoofed email stg-nagomi.fancl.co.jp 18.173.252.85 | -6 |
| TLS / Cryptography | TLS 1.0 Enabled Deprecated TLS 1.0 is still enabled m.fancl.co.jp 101.110.14.193 :443 + 2 other hosts · 3 of 35 SSL hosts (9%) | -1 |
| TLS / Cryptography | TLS 1.1 Enabled Deprecated TLS 1.1 is still enabled m.fancl.co.jp 101.110.14.193 :443 + 2 other hosts · 3 of 35 SSL hosts (9%) | -1 |
| TLS / Cryptography | Expired Certificate SSL/TLS certificate has expired style.fancl.co.jp 219.99.173.232 :443 · 1 of 35 SSL hosts (3%) | -1 |
| Application Hardening | Server Version Disclosed Server header reveals software version information counseling.fancl.co.jp 13.193.174.8 :443 + 2 other hosts · 3 of 37 HTTP hosts (8%) | -1 |
| TLS / Cryptography | SSLv2/SSLv3 Enabled Critically insecure SSL protocols are enabled members.fancl.co.jp 52.192.122.162 :443 · 1 of 35 SSL hosts (3%) | 0 |
| TLS / Cryptography | Self-Signed Certificate Certificate is self-signed (not issued by a trusted CA) m.fancl.co.jp 101.110.14.193 :25 + 1 other host · 2 of 35 SSL hosts (6%) | 0 |
| TLS / Cryptography | Certificate Hostname Mismatch Domain not found in certificate Subject Alternative Names m.fancl.co.jp 101.110.14.193 :25 + 3 other hosts · 4 of 35 SSL hosts (11%) | 0 |
| Category | Signal | Points |
|---|---|---|
| TLS / Cryptography | TLS 1.3 Supported Server supports TLS 1.3 fancl-ns.fancl.co.jp 13.113.17.23 :443 + 25 other hosts · 26 of 35 SSL hosts (74%) | +7 |
| TLS / Cryptography | Strong Ciphers Only Only strong cipher suites detected (ECDHE+AES-GCM/ChaCha20) m.fancl.co.jp 101.110.14.193 :25 | +8 |
| TLS / Cryptography | Valid Certificate SSL/TLS certificate is valid and not expired m.fancl.co.jp 101.110.14.193 :25 + 34 other hosts · 35 of 35 SSL hosts (100%) | +8 |
| TLS / Cryptography | Reputable Certificate Authority Certificate issued by a reputable CA fancl-ns.fancl.co.jp 13.113.17.23 :443 + 28 other hosts · 29 of 35 SSL hosts (83%) | +4 |
| TLS / Cryptography | HSTS Enabled HTTP Strict Transport Security header present ad.fancl.co.jp 143.204.142.27 :443 + 9 other hosts · 10 of 35 SSL hosts (29%) | +2 |
| TLS / Cryptography | OCSP Stapling OCSP stapling is enabled mimg2.fancl.co.jp 101.102.235.60 :443 + 2 other hosts · 3 of 35 SSL hosts (9%) | +0 |
| TLS / Cryptography | PQC-Ready Infrastructure Server supports TLS 1.3 with TLS_AES_256_GCM_SHA384 cipher suite, indicating readiness for post-quantum hybrid key exchange (X25519 + ML-KEM-768) uag2.fancl.co.jp 4.216.205.141 :443 + 3 other hosts · 4 of 35 SSL hosts (11%) | +1 |
| Network Security | WAF/CDN Detected Protected by Fastly stg-nagomi.fancl.co.jp 18.173.252.85 + 18 other hosts · 19 of 37 HTTP hosts (51%) | +8 |
| Network Security | Enterprise Cloud Hosting Hosted on AWS collect.fancl.co.jp 13.114.90.192 | +8 |
| Network Security | Minimal Open Ports Only 3 port(s) open stg-nagomi.fancl.co.jp 18.173.252.85 | +5 |
| Network Security | No High-Risk Ports Detected No high-risk service ports (RDP, Telnet, FTP, etc.) are exposed stg-nagomi.fancl.co.jp 18.173.252.85 | +5 |
| Network Security | No Database Ports Exposed No database ports (MySQL, PostgreSQL, MongoDB, etc.) are exposed stg-nagomi.fancl.co.jp 18.173.252.85 | +5 |
| Application Hardening | No Server Version Disclosure Server header does not reveal software version stg-nagomi.fancl.co.jp 18.173.252.85 + 33 other hosts · 34 of 37 HTTP hosts (92%) | +9 |
| Application Hardening | Content Security Policy CSP header is present expertus01.fancl.co.jp 143.204.142.93 :443 + 2 other hosts · 3 of 37 HTTP hosts (8%) | +1 |
| Application Hardening | X-Frame-Options Clickjacking protection header present ad.fancl.co.jp 143.204.142.27 :443 + 4 other hosts · 5 of 37 HTTP hosts (14%) | +1 |
| Application Hardening | X-Content-Type-Options MIME type sniffing protection present ad.fancl.co.jp 143.204.142.27 :443 + 8 other hosts · 9 of 37 HTTP hosts (24%) | +1 |
| Application Hardening | Referrer-Policy Referrer policy header present ad.fancl.co.jp 143.204.142.27 :443 + 5 other hosts · 6 of 37 HTTP hosts (16%) | +0 |
| Application Hardening | Permissions-Policy Permissions policy header present applink.fancl.co.jp 199.36.158.100 :443 · 1 of 37 HTTP hosts (3%) | +0 |
| Application Hardening | No Default Pages No default/welcome pages detected stg-nagomi.fancl.co.jp 18.173.252.85 + 36 other hosts · 37 of 37 HTTP hosts (100%) | +5 |
| Application Hardening | No Admin Interfaces Exposed No exposed admin panels detected stg-nagomi.fancl.co.jp 18.173.252.85 | +8 |
| Vulnerability Exposure | No Validated CVEs No validated vulnerabilities detected. 98 version-inferred CVEs observed but not validated, so excluded from the score. stg-nagomi.fancl.co.jp 18.173.252.85 | +30 |
| Vulnerability Exposure | No Outdated Software Detected All detected software versions are within acceptable ranges stg-nagomi.fancl.co.jp 18.173.252.85 | +15 |
| Email Security | DMARC Quarantine Policy DMARC policy set to quarantine unauthenticated email stg-nagomi.fancl.co.jp 18.173.252.85 | +10 |
| Email Security | DKIM Record Found DKIM record found (selector: selector1) stg-nagomi.fancl.co.jp 18.173.252.85 | +10 |
17 Critical 47 High 32 Medium 2 Low
Of 64 high-severity (CVSS ≥ 7.0) CVEs, 0 are validated (actively confirmed) and 64 are not validated — inferred from a service version banner only. Only validated CVEs affect the score. Not-validated CVEs are unconfirmed and may be false positives (for example a backported vendor patch that keeps the original version string), so they are excluded from scoring.
These match a reported software version, but validation was inadequate to confirm the vulnerability is present and exploitable. Not counted toward the score. Corroborate (e.g. confirm the running build and patch level) before treating them as real exposure.
| CVE | CVSS | Where |
|---|---|---|
| CVE-2021-44790 | 9.8 | counseling.fancl.co.jp 13.193.174.8:443 |
| CVE-2026-28780 | 9.8 | members.fancl.co.jp 52.192.122.162:443 |
| CVE-2026-29167 | 9.8 | members.fancl.co.jp 52.192.122.162:443 |
| CVE-2022-31813 | 9.8 | counseling.fancl.co.jp 13.193.174.8:443 |
| CVE-2026-44631 | 9.8 | members.fancl.co.jp 52.192.122.162:443 |
| CVE-2021-26691 | 9.8 | counseling.fancl.co.jp 13.193.174.8:443 |
| CVE-2021-39275 | 9.8 | counseling.fancl.co.jp 13.193.174.8:443 |
| CVE-2022-22720 | 9.8 | counseling.fancl.co.jp 13.193.174.8:443 |
| CVE-2022-23943 | 9.8 | counseling.fancl.co.jp 13.193.174.8:443 |
| CVE-2023-25690 | 9.8 | counseling.fancl.co.jp 13.193.174.8:443 |
| CVE-2024-3566 | 9.8 | members.fancl.co.jp 52.192.122.162:443 |
| CVE-2025-23048 | 9.1 | members.fancl.co.jp 52.192.122.162:443 |
| CVE-2022-22721 | 9.1 | counseling.fancl.co.jp 13.193.174.8:443 |
| CVE-2026-42535 | 9.1 | members.fancl.co.jp 52.192.122.162:443 |
| CVE-2022-28615 | 9.1 | counseling.fancl.co.jp 13.193.174.8:443 |
| CVE-2022-36760 | 9.0 | counseling.fancl.co.jp 13.193.174.8:443 |
| CVE-2021-40438 | 9.0 | counseling.fancl.co.jp 13.193.174.8:443 |
| CVE-2026-24072 | 8.8 | members.fancl.co.jp 52.192.122.162:443 |
| CVE-2026-45447 | 8.8 | members.fancl.co.jp 52.192.122.162:80 |
| CVE-2025-58098 | 8.3 | members.fancl.co.jp 52.192.122.162:443 |
| CVE-2021-44224 | 8.2 | counseling.fancl.co.jp 13.193.174.8:443 |
| CVE-2026-7383 | 8.1 | members.fancl.co.jp 52.192.122.162:443 |
| CVE-2023-31122 | 7.5 | counseling.fancl.co.jp 13.193.174.8:443 |
| CVE-2021-36160 | 7.5 | counseling.fancl.co.jp 13.193.174.8:443 |
| CVE-2025-49630 | 7.5 | members.fancl.co.jp 52.192.122.162:443 |
…and 39 more.
| Port | Service | Host | Flag |
|---|---|---|---|
| 80 | CloudFront httpd | stg-nagomi.fancl.co.jp 18.173.252.85 | |
| 80 | Apache httpd | m.fancl.co.jp 101.110.14.193 | |
| 25 | Postfix smtpd | m.fancl.co.jp 101.110.14.193 | |
| 443 | Apache httpd | m.fancl.co.jp 101.110.14.193 | |
| 443 | https | fancl-ns.fancl.co.jp 13.113.17.23 | |
| 80 | CloudFront httpd | ad.fancl.co.jp 143.204.142.27 | |
| 443 | nginx | ad.fancl.co.jp 143.204.142.27 | |
| 443 | Apache httpd | mimg.fancl.co.jp 164.70.8.147 | |
| 80 | CloudFront httpd | nagomi.fancl.co.jp 143.204.142.121 | |
| 443 | CloudFront httpd | nagomi.fancl.co.jp 143.204.142.121 | |
| 80 | http | mimg2.fancl.co.jp 101.102.235.60 | |
| 443 | https | mimg2.fancl.co.jp 101.102.235.60 | |
| 80 | http | suqboc.fancl.co.jp 74.119.117.62 | |
| 443 | https | suqboc.fancl.co.jp 74.119.117.62 | |
| 80 | Apache httpd | faq.fancl.co.jp 124.146.171.25 | |
| 443 | Apache httpd | faq.fancl.co.jp 124.146.171.25 | |
| 80 | http | mama.fancl.co.jp 3.5.155.93 | |
| 80 | CloudFront httpd | expertus03.fancl.co.jp 18.173.252.40 | |
| 80 | http | applink.fancl.co.jp 199.36.158.100 | |
| 443 | https | applink.fancl.co.jp 199.36.158.100 | |
| 80 | http | uag2.fancl.co.jp 4.216.205.141 | |
| 443 | https | uag2.fancl.co.jp 4.216.205.141 | |
| 443 | Apache httpd 2.4.37 | counseling.fancl.co.jp 13.193.174.8 | |
| 80 | Apache httpd | style.fancl.co.jp 219.99.173.232 | |
| 443 | Apache httpd | style.fancl.co.jp 219.99.173.232 | |
| 80 | CloudFront httpd | expertus01.fancl.co.jp 143.204.142.93 | |
| 443 | https | expertus01.fancl.co.jp 143.204.142.93 | |
| 80 | Apache httpd | jinzai.fancl.co.jp 165.76.159.253 | |
| 443 | Apache httpd | jinzai.fancl.co.jp 165.76.159.253 | |
| 80 | CloudFront httpd | staging.ad.fancl.co.jp 18.173.252.39 | |
| 80 | AWS ELB 2.0 | visitor-service.fancl.co.jp 13.193.116.22 | |
| 443 | http | visitor-service.fancl.co.jp 13.193.116.22 | |
| 80 | CloudFront httpd | stg-weather.fancl.co.jp 143.204.142.34 | |
| 80 | CloudFront httpd | www.fancl.co.jp 143.204.142.123 | |
| 443 | https | www.fancl.co.jp 143.204.142.123 | |
| 80 | CloudFront httpd | expertus04.fancl.co.jp 143.204.142.101 | |
| 80 | CloudFront httpd | calo.fancl.co.jp 143.204.142.71 | |
| 443 | nginx | calo.fancl.co.jp 143.204.142.71 | |
| 80 | http | mi.fancl.co.jp 35.153.155.164 | |
| 443 | https | mi.fancl.co.jp 35.153.155.164 |
CloudFront httpdCloudFrontAmazon CloudFrontAmazon Web ServicesPostfix smtpdAZIA Co.,Ltd.Apache httpdApacheApache HTTP ServerNijimo K.K.AmazonnginxSectigo LimitedNijimo, Inc.AmazonS3Amazon S3AWS S3VarnishHTTP/3HSTSGoogle Tag ManagerFirebaseAlpine.jsGoogle Trust ServicesMicrosoft CorporationApache httpd 2.4.37Apache 2.4.37DigiCert Inc2.4.37PleskLet's EncryptAWS ELB 2.0awselb 2.0Amazon ELBenvoyApache httpd 2.4.58Apache 2.4.58Apache HTTP Server 2.4.58Ubuntu2.4.58Apache httpd 2.4.63Apache 2.4.63UNIXPHP 5.4.16Apache HTTP Server 2.4.63OpenSSL 1.0.2k2.4.631.0.2k5.4.16Cybertrust Japan Co., Ltd.jagSECOM Trust Systems Co., Ltd.CloudflareGlobalSign nv-saAWSImpervaAzureGCP
The FairSRS Score is a free security rating from 0 to 100 that measures a company’s externally observable security posture - the same outside-in signals a security team (or an attacker) can see without any access to the target’s internal systems. Enter any company domain above and FairSRS scans publicly available data to grade its third-party and vendor security risk in seconds, then generates a shareable report you can download as a PDF.
It’s powered by the free, open-source Fair TPRM platform and the same continuous security monitoring engine used inside our vendor risk management workflows - so the rating you see here is the same one security teams rely on to monitor their vendors.
Your FairSRS Score is a weighted blend of five externally observable security categories:
Each finding is a signal that adds or subtracts points, producing a 0-100 score and an A-F grade. To turn these signals into quantified financial risk, pair them with FAIR risk analysis and a full GRC compliance program.
Every domain below has a saved FairSRS Score you can open directly - no scan, no waiting, ranked highest score to lowest. Scores reflect the most recent scan and are re-checked when someone re-scans the domain.
Yes. FairSRS is completely free with no login, account, or credit card required. It is powered by the free, open-source Fair TPRM platform.
It measures a company’s externally observable security posture across five categories - TLS/cryptography, network security, application hardening, vulnerability (CVE) exposure, and email security - and combines them into a 0-100 score with an A-F grade.
FairSRS analyzes publicly observable data about a domain - open services, TLS and certificate configuration, security headers, known CVEs, and DNS-based email protections such as SPF, DKIM and DMARC - and weights each signal to produce the score. No login or access to the target is required.
Yes. No account is needed, and if you choose to have the report emailed, your address is used only to send that one report, encrypted in transit, then permanently deleted. We never store it, never sell or share it, and no one from Fair TPRM will contact you.
Yes. Enter any public company domain to check its external security posture. It is designed to help you assess third-party vendors and suppliers.
A security rating provides signals to help identify risk, but it is not a complete picture and should not be the sole basis for judging a company’s security. Some organizations run deception technology that can appear vulnerable but reflects a mature program. Always corroborate with direct assessment.