gcpay.com security report

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

36risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

3Medium

5Low

1Info

Collected 21 hours ago4.3sfrom cache

Certificate Transparency16
DNS resolution38
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs44
Registration
DNS posture4
Email authentication2
Certificate
Security headers0
Archived URLs
Analysis9

noteFound 26 addresses; enriching the first 12.
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.
note2 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

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://ww3.gcpay.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://ww3.gcpay.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://ww3.gcpay.com/
info-test.gcpay.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: info-test.gcpay.com
demo.gcpay.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.gcpay.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://ww3.gcpay.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://ww3.gcpay.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: gcpay.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: gcpay.com

final https://ww3.gcpay.com/status 200time 2556msstack cloudflare · WP Engine · Elementor 4.2.1; settings: css_print_method-external, google_font-enabled, font_display-auto

✓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

✓Receives mail via 1 server
gcpay-com.mail.protection.outlook.com
✓SPFends in -all
v=spf1 include:spf.protection.outlook.com include:4314135.spf10.hubspotemail.net include:spf.mandrillapp.com -all
✓DMARCp=quarantine
v=DMARC1; p=quarantine; rua=mailto:dmarc_agg@vali.email;
✓MTA-STSinbound mail must use TLS

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
ns-1403.awsdns-47.org ns-1697.awsdns-20.co.uk ns-92.awsdns-11.com ns-924.awsdns-51.net

✓Registered with CSC Corporate Domains, Inc.26.5 years old
gcpay.com
✓Registration expiry552 days
2028-03-11
✓Transfer lock
client transfer prohibited
✓4 nameservers at registry
ns-1403.awsdns-47.org ns-1697.awsdns-20.co.uk ns-92.awsdns-11.com ns-924.awsdns-51.net

Address	Ports	Edge	Network
104.18.34.21 info-test.gcpay.com +3	80443205220532082208320862087+5	Cloudflare~	—
172.64.153.235 info-test.gcpay.com +3	80443205220532082208320862087+5	Cloudflare~	—
35.153.193.207 gcpay.com +2	80443	direct	—
100.57.70.224 gcpay.com +2	80443	direct	—
34.237.146.177 gcpay.com +2	80443	direct	—
18.211.205.17 gcpay.com +2	80443	direct	—
18.210.225.7 gcpay.com +2	80443	direct	—
34.41.225.193 ww3.gcpay.com +3	80443	direct	—
54.81.144.249 demo.gcpay.com +1	80443	direct	—
100.27.93.137 demo.gcpay.com +3	80443	direct	—
52.54.140.157 demo.gcpay.com +2	80443	direct	—
52.21.161.112 gcpay.com +1	none known	direct	—

Archived URLs

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

gcpay.com security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames