← All Results
Domain History

infocentral.heartlandpaymentsystems.com

Grade D- · 41/100 · 4/7 security headers present

Security Score

D-
41/ 100

Security Headers

4/ 7

CSP Violations

NoViolations

Issues Found

17Issues

Recommendations

4Available

Security

41 / 100

Significant security weaknesses detected in CSP configuration.

Compliance

65 / 100

Several compliance gaps found in CSP implementation.

Best Practices

20 / 100

Best practices largely absent — review CSP configuration.

CSP Analysis

Content Security PolicyHIGH
default-src 'self';          connect-src 'self' https:     https://app.pendo.io     https://data.pendo.io      wss://webmessaging.usw2.pure.cloud/     wss://webmessaging.mypurecloud.com/     https://apps.usw2.pure.cloud     https://apps.mypurecloud.com/     https://pendo-static-5377907697778688.storage.googleapis.com;     font-src 'self' https://fonts.googleapis.com/ https://fonts.gstatic.com/ data:;      frame-ancestors https://app.pendo.io/;     frame-src 'self'      https://app.pendo.io/      https://il01merchantportals.propay.com/      https://apps.usw2.pure.cloud     https://apps.mypurecloud.com/     https://propay.merchant-portals.com/      https://gateway.zscloud.net/      *.hlprd.com/;          img-src 'self'      https://data.pendo.io/      https://*.hlprd.com/      https://il01merchantportals.propay.com/      https://propay.merchant-portals.com/      https://cdn.pendo.io/     https://app.pendo.io/      https://pendo-static-5377907697778688.storage.googleapis.com/  data:;                  media-src 'self'; object-src 'unsafe-inline' 'unsafe-eval' 'self'; script-src 'unsafe-inline' 'unsafe-eval' 'self'      https://www.google-analytics.com      https://apps.usw2.pure.cloud     https://apps.mypurecloud.com/     https://gateway.zscloud.net     https://app.pendo.io/      https://cdn.pendo.io/      https://data.pendo.io/      https://*.hlprd.com/      https://www.googletagmanager.com/        https://pendo-io-static.storage.googleapis.com/      https://pendo-static-5377907697778688.storage.googleapis.com/;       style-src 'unsafe-inline' 'self'      https://cdn.pendo.io/     https://app.pendo.io      https://pendo-static-5377907697778688.storage.googleapis.com         https://*.hlprd.com/      https://fonts.googleapis.com/;      child-src 'unsafe-inline' 'unsafe-eval' 'self' https://fonts.googleapis.com/ https://app.pendo.io/ ;
Directive Analysis
default-srcLOW
self
connect-srcHIGH
self https: https://app.pendo.io https://data.pendo.io wss://webmessaging.usw2.pure.cloud/ wss://webmessaging.mypurecloud.com/ https://apps.usw2.pure.cloud https://apps.mypurecloud.com/ https://pendo-static-5377907697778688.storage.googleapis.com
•CRITICAL: 'https:' in connect-src allows scripts from ANY HTTPS domain
font-srcLOW
self https://fonts.googleapis.com/ https://fonts.gstatic.com/ data:
•Info: 'data:' URI in font-src
frame-ancestorsLOW
https://app.pendo.io/
frame-srcMEDIUM
self https://app.pendo.io/ https://il01merchantportals.propay.com/ https://apps.usw2.pure.cloud https://apps.mypurecloud.com/ https://propay.merchant-portals.com/ https://gateway.zscloud.net/ *.hlprd.com/
•Subdomain wildcard '*.hlprd.com/' in frame-src - vulnerable to subdomain takeover
img-srcLOW
self https://data.pendo.io/ https://*.hlprd.com/ https://il01merchantportals.propay.com/ https://propay.merchant-portals.com/ https://cdn.pendo.io/ https://app.pendo.io/ https://pendo-static-5377907697778688.storage.googleapis.com/ data:
•Info: 'data:' URI in img-src
media-srcLOW
self
object-srcHIGH
unsafe-inline unsafe-eval self
•Unsafe inline execution allowed in object-src
•Unsafe eval() execution allowed in object-src
script-srcHIGH
unsafe-inline unsafe-eval self https://www.google-analytics.com https://apps.usw2.pure.cloud https://apps.mypurecloud.com/ https://gateway.zscloud.net https://app.pendo.io/ https://cdn.pendo.io/ https://data.pendo.io/ https://*.hlprd.com/ https://www.googletagmanager.com/ https://pendo-io-static.storage.googleapis.com/ https://pendo-static-5377907697778688.storage.googleapis.com/
•Unsafe inline execution allowed in script-src
•Unsafe eval() execution allowed in script-src
•No nonces or hashes used for script-src
style-srcHIGH
unsafe-inline self https://cdn.pendo.io/ https://app.pendo.io https://pendo-static-5377907697778688.storage.googleapis.com https://*.hlprd.com/ https://fonts.googleapis.com/
•Unsafe inline execution allowed in style-src
child-srcHIGH
unsafe-inline unsafe-eval self https://fonts.googleapis.com/ https://app.pendo.io/
•Unsafe inline execution allowed in child-src
•Unsafe eval() execution allowed in child-src
Missing Directives
⚠HIGHMissing HIGH directive base-uri (Base URI control - prevents base tag injection)
⚠MEDIUMMissing MEDIUM directive form-action (Form submission control - prevents form hijacking)

Security Headers

✗Cross-Origin-Opener-PolicyMissing

Isolates the browsing context to prevent Spectre-type side-channel attacks and cross-origin window manipulation.

How to add it:

nginx
add_header Cross-Origin-Opener-Policy "same-origin" always;
apache
Header always set Cross-Origin-Opener-Policy "same-origin"
cloudflare
Rules > Transform Rules > HTTP Response Header Modification > Set Cross-Origin-Opener-Policy to "same-origin"
✗Permissions-PolicyMissing

Restricts which browser features (camera, microphone, geolocation) the page can use, limiting attack surface.

How to add it:

nginx
add_header Permissions-Policy "camera=(), microphone=(), geolocation=()" always;
apache
Header always set Permissions-Policy "camera=(), microphone=(), geolocation=()"
cloudflare
Rules > Transform Rules > HTTP Response Header Modification > Set Permissions-Policy value
✗Referrer-PolicyMissing

Controls how much referrer information is sent with requests, preventing data leaks to third parties.

How to add it:

nginx
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
apache
Header always set Referrer-Policy "strict-origin-when-cross-origin"
cloudflare
Rules > Transform Rules > HTTP Response Header Modification > Set Referrer-Policy to "strict-origin-when-cross-origin"
✓Strict-Transport-SecurityPresent

max-age=31536000; includeSubDomains;

Forces browsers to use HTTPS for all future requests, preventing man-in-the-middle attacks and SSL stripping.

✓X-Content-Type-OptionsPresent

nosniff

Prevents browsers from MIME-sniffing responses away from the declared Content-Type, blocking drive-by downloads.

✓X-Frame-OptionsPresent

SAMEORIGIN

Prevents the page from being embedded in iframes, protecting against clickjacking attacks.

✓X-XSS-ProtectionPresent

1; mode=block

Legacy XSS filter for older browsers. Modern browsers use CSP instead. Set to "0" to avoid false positives.

3 recommended security headers are missing on infocentral.heartlandpaymentsystems.com.

Issues Found

  • •CRITICAL: 'https:' in connect-src allows scripts from ANY HTTPS domaincritical
  • •Info: 'data:' URI in font-srcinfo
  • •Info: 'data:' URI in img-srcinfo
  • •Missing HIGH directive base-uri (Base URI control - prevents base tag injection)high
  • •Missing MEDIUM directive form-action (Form submission control - prevents form hijacking)medium
  • •Missing security header: Cross-Origin-Opener-Policymedium
  • •Missing security header: Permissions-Policymedium
  • •Missing security header: Referrer-Policymedium
  • •No nonces or hashes used for script-srcmedium
  • •Subdomain wildcard '*.hlprd.com/' in frame-src - vulnerable to subdomain takeovermedium
  • •Unsafe eval() execution allowed in child-srchigh
  • •Unsafe eval() execution allowed in object-srchigh
  • •Unsafe eval() execution allowed in script-srchigh
  • •Unsafe inline execution allowed in child-srchigh
  • •Unsafe inline execution allowed in object-srchigh
  • •Unsafe inline execution allowed in script-srchigh
  • •Unsafe inline execution allowed in style-srchigh

Recommendations

  • →Add base-uri directive with appropriate restrictions
  • →Add form-action directive with appropriate restrictions
  • →Consider implementing a stricter Content Security Policy
  • →Replace wildcards (*) with specific source lists

Beyond headers: infrastructure exposure

via OSN, our sister project

Security headers protect the browser. OSN maps what's exposed underneath — servers, open ports, known CVEs, DNS and WHOIS.

See what the internet sees about infocentral.heartlandpaymentsystems.comWeak headers often come with other exposure — check the full picture.

infocentral.heartlandpaymentsystems.com

1 scan since 6/25/2026

D-

Latest: 41/100

Total Scans

1

Latest Score

41/100

First Scan

6/25/2026

Last Scan

6/25/2026

Security

41 / 100

Significant security weaknesses detected in CSP configuration.

Compliance

65 / 100

Several compliance gaps found in CSP implementation.

Best Practices

20 / 100

Best practices largely absent — review CSP configuration.

Scan History

DateScoreCSPHeadersIssuesAction
Jun 25, 2026
D- (41)
Yes
4/717View →

Show off your security grade

Embed this badge on your site or README. It updates automatically after each scan and links back to this report.

HeaderTest security grade: D- (41/100) for infocentral.heartlandpaymentsystems.com
HTML
<a href="https://headertest.com/results/infocentral.heartlandpaymentsystems.com" title="Security headers grade for infocentral.heartlandpaymentsystems.com — HeaderTest">
  <img src="https://headertest.com/api/badge/infocentral.heartlandpaymentsystems.com" alt="HeaderTest security grade: D- (41/100) for infocentral.heartlandpaymentsystems.com" />
</a>
Markdown
[![HeaderTest security grade: D- (41/100) for infocentral.heartlandpaymentsystems.com](https://headertest.com/api/badge/infocentral.heartlandpaymentsystems.com)](https://headertest.com/results/infocentral.heartlandpaymentsystems.com)
infocentral.heartlandpay… Security Headers — Scan History | HeaderTest