Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
golinks.io scored 82/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: Known Breaches, DMARC / Email Security, HSTS Header all passed.
3 action items identified, including 0 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How golinks.io compares
Grade distribution across 2378 companies we've scanned. golinks.io scores better than 72% of them.
71
A+
22
A
180
A-
181
B+
69
B
333
B-
111
C+
111
C
295
C-
110
D+
92
D
216
D-
587
F
golinks.io — Grade B- (82/100)
2378 companies scanned
Security checks
Each check inspects a different part of golinks.io's public security setup. Green means healthy, yellow needs attention, red is a problem.
DNS Configuration
Strengths: 4 nameservers configured (ns-1506.awsdns-60.org., ns-1786.awsdns-31.co.uk., ns-277.awsdns-34.com., ns-590.awsdns-09.net.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
TLS Configuration
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
Certificate Hygiene
Strengths: Certificate valid, 297 days remaining; Issued by GoDaddy.com, Inc.. Issues: Wildcard certificate in use — broader attack surface if compromised.
Known Breaches
No known breaches found in public disclosure databases.
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google).
HSTS Header
HSTS enabled: max-age=63072000. includeSubDomains present. Missing preload directive.
Security Headers
All 5 recommended security headers present: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy.
CVE Exposure
Detected technologies: Apache. No version information exposed — CVE matching not possible (this is good practice).
Recommended actions
3 items
Steps to improve golinks.io's security grade, ranked by impact.
1
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for golinks.io can be spoofed, potentially redirecting users to malicious sites. This requires coordination with your domain registrar to publish DS records.
Compliance impact
NIST 800-53SC-20
Secure name/address resolution service
How to fix this
1
Check if your DNS provider supports DNSSEC (Cloudflare, Route53, etc.)
2
Enable DNSSEC signing in your DNS provider dashboard
3
Add the DS record to your registrar for .io TLD
4
Verify: dig +dnssec golinks.io
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Upgrade to TLS 1.3
golinks.io negotiated TLSv1.2. TLS 1.2 is still compliant under all major security frameworks and is not a vulnerability. TLS 1.3 offers faster handshakes and removes legacy cipher negotiation. This is a best-practice improvement, not a compliance gap.
How to fix this
1
Update web server config to prefer TLS 1.3 (nginx: ssl_protocols TLSv1.2 TLSv1.3)
2
Verify: openssl s_client -connect golinks.io:443 -tls1_3
3
Review certificate configuration
Certificate issues found for golinks.io: wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. These are operational hygiene items, not immediate security risks.
How to fix this
1
Consider replacing wildcard cert with individual certs for critical subdomains
2
Consolidate certificate issuance to 1–2 trusted CAs
At a glance
Key data points from the scan.
TLS Version
TLSv1.2
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
DMARC Policy
p=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google).
SPF Record
Present
v=spf1 include:_spf.google.com include:_spf.salesforce.com include:4486639.spf04.hubspotemail.net ~a
Security Headers
5/5 present
All headers configured.
HSTS
Enabled
HSTS enabled: max-age=63072000. includeSubDomains present. Missing preload directive.
SSL Certificate
Issues
Strengths: Certificate valid, 297 days remaining; Issued by GoDaddy.com, Inc.. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-1506.awsdns-60.org., ns-1786.awsdns-31.co.uk., ns-277.awsdns-34.com., ns-590.awsdns-09.net.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.