smu.edu Security Score

FairSRS Score 54/100 · Grade F · last scanned Jul 10, 2026

Powered by Shodan, tuned by FairTPRM!

Scanning external signals… this can take up to a couple of minutes.

Download PDF report

FairSRS Score - smu.edu

54/100
FairSRS Score
F
Grade
Needs Improvement
Signal Rating
21 positive signals
8 risk signals
94 host(s), 100 subdomain(s)
Scan coverage. This report analyzed smu.edu plus a random sample of 100 of its 943 discovered subdomains (up to 100 subdomains are checked per scan). The score reflects this sampled portion of the external attack surface, so re-scanning may surface additional hosts.

Category Breakdown

Categories with items of opportunity are clickable - open one to see the action items that would raise its score.

65/100
69/100
74/100
0/100
59/100

Security Signals

Risk Signals (8)

CategorySignalPoints
Vulnerability ExposureCritical CVEs (22)
22 critical vulnerabilities detected (CVSS >= 9.0)
idp2.smu.edu 129.119.70.141
-45
Vulnerability ExposureHigh CVEs (65)
65 high-severity vulnerabilities detected (CVSS 7.0-8.9)
idp2.smu.edu 129.119.70.141
-30
Vulnerability ExposureMedium CVEs (40)
40 medium-severity vulnerabilities detected (CVSS 4.0-6.9)
idp2.smu.edu 129.119.70.141
-20
Email SecurityOpen SMTP (Port 25)
SMTP port 25 is open -- potential for email relay abuse
comms.smu.edu 13.110.204.15 :25
-8
Email SecuritySPF Soft Fail (~all)
SPF record uses soft fail (~all) instead of hard fail (-all) -- mail servers may still accept spoofed email
idp2.smu.edu 129.119.70.141
-6
Vulnerability ExposureLow CVEs (3)
3 low-severity vulnerabilities detected (CVSS < 4.0)
idp2.smu.edu 129.119.70.141
-3
TLS / CryptographyCertificate Hostname Mismatch
Domain not found in certificate Subject Alternative Names
vpn-s.smu.edu 129.119.235.251 :443 + 6 other hosts · 7 of 22 SSL hosts (32%)
-1
Application HardeningServer Version Disclosed
Server header reveals software version information
ftp1.economics.smu.edu 129.119.70.26 :80 + 2 other hosts · 3 of 21 HTTP hosts (14%)
-1

Positive Signals (21)

CategorySignalPoints
TLS / CryptographyTLS 1.3 Supported
Server supports TLS 1.3
vpn-s.smu.edu 129.119.235.251 :443 + 2 other hosts · 3 of 22 SSL hosts (14%)
+1
TLS / CryptographyStrong Ciphers Only
Only strong cipher suites detected (ECDHE+AES-GCM/ChaCha20)
idp2.smu.edu 129.119.70.141 :443
+8
TLS / CryptographyValid Certificate
SSL/TLS certificate is valid and not expired
idp2.smu.edu 129.119.70.141 :443 + 12 other hosts · 13 of 22 SSL hosts (59%)
+5
TLS / CryptographyReputable Certificate Authority
Certificate issued by a reputable CA
codingbootcamp.smu.edu 18.208.13.117 :443 + 4 other hosts · 5 of 22 SSL hosts (23%)
+1
TLS / CryptographyHSTS Enabled
HTTP Strict Transport Security header present
idp2.smu.edu 129.119.70.141 :443 + 3 other hosts · 4 of 22 SSL hosts (18%)
+1
TLS / CryptographyPQC-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)
buslibguides.smu.edu 54.88.35.99 :443 · 1 of 22 SSL hosts (5%)
+0
Network SecurityWAF/CDN Detected
Protected by AWS ELB
codingbootcamp.smu.edu 18.208.13.117 + 1 other host · 2 of 21 HTTP hosts (10%)
+1
Network SecurityEnterprise Cloud Hosting
Hosted on AWS
buslibguides.smu.edu 54.88.35.99
+8
Network SecurityNo High-Risk Ports Detected
No high-risk service ports (RDP, Telnet, FTP, etc.) are exposed
idp2.smu.edu 129.119.70.141
+5
Network SecurityNo Database Ports Exposed
No database ports (MySQL, PostgreSQL, MongoDB, etc.) are exposed
idp2.smu.edu 129.119.70.141
+5
Application HardeningNo Server Version Disclosure
Server header does not reveal software version
idp2.smu.edu 129.119.70.141 + 17 other hosts · 18 of 21 HTTP hosts (86%)
+9
Application HardeningContent Security Policy
CSP header is present
vpn-s.smu.edu 129.119.235.251 :80 + 1 other host · 2 of 21 HTTP hosts (10%)
+1
Application HardeningX-Frame-Options
Clickjacking protection header present
vpn-s.smu.edu 129.119.235.251 :80 + 4 other hosts · 5 of 21 HTTP hosts (24%)
+1
Application HardeningX-Content-Type-Options
MIME type sniffing protection present
vpn-s.smu.edu 129.119.235.251 :80 + 3 other hosts · 4 of 21 HTTP hosts (19%)
+1
Application HardeningReferrer-Policy
Referrer policy header present
hcmreports.smu.edu 129.119.70.147 :443 · 1 of 21 HTTP hosts (5%)
+0
Application HardeningNo Default Pages
No default/welcome pages detected
idp2.smu.edu 129.119.70.141 + 20 other hosts · 21 of 21 HTTP hosts (100%)
+5
Application HardeningNo Admin Interfaces Exposed
No exposed admin panels detected
idp2.smu.edu 129.119.70.141
+8
Vulnerability ExposureNo Outdated Software Detected
All detected software versions are within acceptable ranges
idp2.smu.edu 129.119.70.141
+15
Email SecurityDMARC Monitor-Only
DMARC policy set to none (monitoring only)
idp2.smu.edu 129.119.70.141
+3
Email SecurityDKIM Record Found
DKIM record found (selector: selector1)
idp2.smu.edu 129.119.70.141
+10
Email SecurityEnterprise Email Gateway
Email protected by Microsoft EOP
idp2.smu.edu 129.119.70.141
+10

Vulnerability Exposure

22 Critical 65 High 40 Medium 3 Low

CVECVSSWhere
CVE-2024-384769.8ftp1.economics.smu.edu 129.119.70.26:80
CVE-2021-447909.8ftp1.economics.smu.edu 129.119.70.26:80
CVE-2026-287809.8sdars60.systems.smu.edu 129.119.70.60:443
CVE-2026-291679.8sdars60.systems.smu.edu 129.119.70.60:443
CVE-2022-318139.8ftp1.economics.smu.edu 129.119.70.26:80
CVE-2026-446319.8sdars60.systems.smu.edu 129.119.70.60:443
CVE-2021-266919.8ftp1.economics.smu.edu 129.119.70.26:80
CVE-2024-384749.8ftp1.economics.smu.edu 129.119.70.26:80
CVE-2021-392759.8ftp1.economics.smu.edu 129.119.70.26:80
CVE-2021-37119.8ftp1.economics.smu.edu 129.119.70.26:80
CVE-2022-239439.8ftp1.economics.smu.edu 129.119.70.26:80
CVE-2022-227209.8ftp1.economics.smu.edu 129.119.70.26:80
CVE-2023-256909.8ftp1.economics.smu.edu 129.119.70.26:80
CVE-2026-317899.8sdars60.systems.smu.edu 129.119.70.60:443
CVE-2024-384759.1ftp1.economics.smu.edu 129.119.70.26:80
CVE-2025-230489.1sdars60.systems.smu.edu 129.119.70.60:443
CVE-2022-227219.1ftp1.economics.smu.edu 129.119.70.26:80
CVE-2026-425359.1sdars60.systems.smu.edu 129.119.70.60:443
CVE-2022-286159.1ftp1.economics.smu.edu 129.119.70.26:80
CVE-2026-341829.1sdars60.systems.smu.edu 129.119.70.60:443
CVE-2022-367609.0ftp1.economics.smu.edu 129.119.70.26:80
CVE-2021-404389.0ftp1.economics.smu.edu 129.119.70.26:80
CVE-2026-454478.8sdars60.systems.smu.edu 129.119.70.60:443
CVE-2026-240728.8sdars60.systems.smu.edu 129.119.70.60:443
CVE-2025-154678.8sdars60.systems.smu.edu 129.119.70.60:443

…and 62 more high-severity CVEs.

Open Ports & Services

PortServiceHostFlag
443httpsidp2.smu.edu 129.119.70.141
80Apache httpd 2.4.37ftp1.economics.smu.edu 129.119.70.26
443httpsftp1.economics.smu.edu 129.119.70.26
80httpvpn-s.smu.edu 129.119.235.251
443httpsvpn-s.smu.edu 129.119.235.251
80AWS ELB 2.0codingbootcamp.smu.edu 18.208.13.117
443AWS ELB 2.0codingbootcamp.smu.edu 18.208.13.117
80httpcoxrenovation.smu.edu 35.71.150.51
443httpscoxrenovation.smu.edu 35.71.150.51
25Postfix smtpdcomms.smu.edu 13.110.204.15
80httpwww.giving.smu.edu 129.119.70.70
443httpswww.giving.smu.edu 129.119.70.70
80AWS ELB 2.0apply.guildhall.smu.edu 18.213.182.107
443AWS ELB 2.0apply.guildhall.smu.edu 18.213.182.107
80httpsmu.edu 129.119.70.169
443httpssmu.edu 129.119.70.169
80httpsdars95.systems.smu.edu 129.119.70.238
443httpssdars95.systems.smu.edu 129.119.70.238
9191http-simple-newsdars95.systems.smu.edu 129.119.70.238
80Apache httpd 2.4.62sdars60.systems.smu.edu 129.119.70.60
443Apache httpd 2.4.62sdars60.systems.smu.edu 129.119.70.60
80httpcape.smu.edu 34.237.219.119
443httpscape.smu.edu 34.237.219.119
80httpbuslibguides.smu.edu 54.88.35.99
443httpsbuslibguides.smu.edu 54.88.35.99
80httphcmreports.smu.edu 129.119.70.147
443Citrix Netscalerhcmreports.smu.edu 129.119.70.147
80httpsdars59.systems.smu.edu 129.119.70.59
443httpssdars59.systems.smu.edu 129.119.70.59

Technology Inventory

HSTSInternet2Apache httpd 2.4.37Apache 2.4.372.4.371.1.1kAWS ELB 2.0awselb 2.0Amazonheroku-routerPostfix smtpdDigiCert IncMicrosoft-IIS 10.0Sectigo LimitedApache httpd 2.4.62Apache 2.4.62Apache HTTP Server 2.4.62OpenSSL 3.5.12.4.623.5.1nginxLet's EncryptCitrix NetscalerOracle Dynamic Monitoring ServiceJavaOracle WebLogic ServerAWSMicrosoft EOP

Important - how to read this rating. Security Rating Services (SRS) like FairSRS provide signals to help identify potential third-party risk from externally observable data. They should not be relied upon as the sole measure of an organization’s security posture. External signals are incomplete by nature. In particular, some organizations deliberately run deception technology (honeypots and decoy services) that is designed to appear vulnerable to lure and study attackers - such systems may surface here as risk signals but can actually reflect a mature, positive security program. Always corroborate these signals with direct assessment and evidence before drawing conclusions.

What is the FairSRS Score?

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.

What the score measures

Your FairSRS Score is a weighted blend of five externally observable security categories:

  • TLS / Cryptography - TLS protocol versions, certificate validity, HSTS, cipher strength, and post-quantum readiness.
  • Network Security - open ports, exposed services, WAF/CDN protection, and hosting posture.
  • Application Hardening - security headers, software version disclosure, exposed admin panels, and directory listings.
  • Vulnerability Exposure - known CVEs on internet-facing services, weighted by severity.
  • Email Security - SPF, DKIM, DMARC, and MTA-STS configuration that protects against spoofing.

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.

Recently scored vendors

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.

Frequently asked questions

Is the FairSRS vendor security score really free?

Yes. FairSRS is completely free with no login, account, or credit card required. It is powered by the free, open-source Fair TPRM platform.

What does the FairSRS Score measure?

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.

How is the score calculated?

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.

Is my data private?

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.

Can I scan any company or vendor?

Yes. Enter any public company domain to check its external security posture. It is designed to help you assess third-party vendors and suppliers.

How accurate is an external security rating?

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.