Summary of facultyaffairs.unc.edu [Desktop version] Website Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 4th, 2026 06:25 GMT+0
Server IP:23.185.0.4
Reverse DNS:-
Location:Mount Hope, United States
Version:for desktop
Your final score:
- A
- B
- C
- F
B+
Test Results Summary for facultyaffairs.unc.edu
- 8 third-party web software dependancies were identified, including 3 outdated dependancies. No known vulnerabilities were detected. 5 identified third-party web software dependancies have unknown versions. The CMS (WordPress) was identified, however, its version could not be determined. The following CMS components, JS-libraries or frameworks were identified: jquery, modernizr, jquery-migrate, and others. Show details.
- No obvious GDPR-related compliance issues were detected across Privacy Policy, Website Security, TLS Encryption, Cookie Protection, Cookie Disclaimer. Show details.
- The website is compliant with PCI DSS Requirement 6.3, while being non-compliant with Requirement 6.4. Show details.
- Issues were identified with key security headers: missing Content-Security-Policy, X-Content-Type-Options, X-Frame-Options. Optional HTTP headers appear to be properly configured: Server, Cache-Control. Show details.
- Content-Security-Policy headers are not present. Show details.
- 4 cookies detected; _ga_374WFH7VBB, nmstat, _ga, _ga_841ZWBEGME have security or privacy-related configuration issues. Show details.
- 25 external requests detected; 2 requests failed. SRI is not used for 12 third-party JavaScript and CSS files. Show details.
- 9 robots.txt rules, 1 User-Agent block and 7 bot protection mechanisms detected. No protection detected via meta restrictions. Show details.
Compliance Summary for facultyaffairs.unc.edu
- GDPR Compliance Passed: No obvious GDPR-related compliance issues were detected across Privacy Policy, Website Security, TLS Encryption, Cookie Protection, Cookie Disclaimer.
- PCI DSS Compliance Failed: The website is compliant with PCI DSS Requirement 6.3, while being non-compliant with Requirement 6.4.