Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
trigger.io scored 35/100 and does not meet the minimum security posture threshold. The most critical issue is: Fix DNS security vulnerabilities — zone transfer exposed. This must be addressed before the vendor can be approved for procurement or data processing activities.
Critical gaps in: DNS Configuration, TLS Configuration, DMARC / Email Security. Positive signals: Known Breaches, CVE Exposure all passed.
4 action items identified, including 3 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How trigger.io compares
Grade distribution across 2378 companies we've scanned. trigger.io scores better than 0% 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
trigger.io — Grade F (35/100)
2378 companies scanned
Security checks
Each check inspects a different part of trigger.io's public security setup. Green means healthy, yellow needs attention, red is a problem.
DNS Configuration
Strengths: 2 nameservers configured (ns2.afraid.org., kali.spacetechnology.net.); 3 MX records present. Issues: DNSSEC not configured — DNS responses can be spoofed; Zone transfer (AXFR) allowed on: kali.spacetechnology.net. — full zone data exposed.
TLS Configuration
TLS certificate verification failed on trigger.io: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 'trigger.io'. (_ssl.c:1081)
DMARC / Email Security
Strengths: SPF record present with soft-fail (~all). Issues: No DMARC record found — email spoofing is not prevented; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
Certificate Hygiene
Issues: Could not retrieve certificate details.
HSTS Header
Could not fetch https://trigger.io — connection failed or timed out.
Security Headers
Could not fetch https://trigger.io — connection failed or timed out.
Known Breaches
No known breaches found in public disclosure databases.
CVE Exposure
No server software versions detected in HTTP response headers. This is good practice (version hiding) but means CVE exposure cannot be assessed from external signals alone.
Recommended actions
4 items
Steps to improve trigger.io's security grade, ranked by impact.
1
Fix DNS security vulnerabilities — zone transfer exposed
Zone transfer (AXFR) is allowed on nameservers for trigger.io, exposing your full DNS zone data to attackers. Critical DNS configuration issues were found that require immediate attention.
Compliance impact
NIST 800-53SC-20
Secure name/address resolution
SOC 2CC6.1
Network security controls
How to fix this
1
Restrict zone transfers to authorized secondary nameservers only
2
Enable DNSSEC signing
3
Ensure at least 2 geographically distributed nameservers
4
Verify zone transfers are blocked: dig AXFR trigger.io @ns1
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 TLS — deprecated protocol in use
trigger.io is using unknown, which is deprecated and has known vulnerabilities. This is a compliance failure under PCI-DSS, HIPAA, and NIST guidelines. Immediate upgrade to TLS 1.2 minimum (TLS 1.3 preferred) is required.
Compliance impact
PCI-DSS 4.0Req 4.2.1
Strong cryptography for transmission
NIST 800-52r2§3.4
TLS 1.0/1.1 must not be used
HIPAA§164.312(e)
Transmission security
How to fix this
1
Disable TLS 1.0 and 1.1 in your web server configuration
2
Enable TLS 1.2 and 1.3: ssl_protocols TLSv1.2 TLSv1.3
3
Remove weak ciphers: ssl_ciphers 'ECDHE-ECDSA-AES128-GCM-SHA256:...'
4
Verify: openssl s_client -connect trigger.io:443 -tls1_2
3
Set up email authentication (DMARC, DKIM)
Without email authentication, anyone can send emails that appear to come from trigger.io. This is the most common vector for phishing attacks targeting employees and customers. DMARC, DKIM are not configured.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
ISO 27001A.13.2.1
Information transfer policies require email security controls
HIPAA§164.312(e)
Transmission security for electronic PHI
How to fix this
1
Add SPF record to DNS: v=spf1 include:_spf.google.com ~all (adjust for your email provider)
2
Configure DKIM signing with your email provider and publish the public key in DNS
3
Add DMARC record: v=DMARC1; p=quarantine; rua=mailto:[email protected]
4
Monitor DMARC reports for 2–4 weeks, then upgrade policy to p=reject
4
Review certificate configuration
Certificate issues found for trigger.io: . These are operational hygiene items, not immediate security risks.
How to fix this
1
Consolidate certificate issuance to 1–2 trusted CAs
At a glance
Key data points from the scan.
TLS Version
Issues detected
TLS certificate verification failed on trigger.io: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 'trigger.io'. (_ssl.c:1081)
DMARC Policy
Not configured
Strengths: SPF record present with soft-fail (~all). Issues: No DMARC record found — email spoofing is not prevented; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
SPF Record
Present
v=spf1 include:zoho.com +a +mx +ip4:164.138.25.158 ~all
Security Headers
0/0 present
All headers configured.
HSTS
Not enabled
Could not fetch https://trigger.io — connection failed or timed out.
SSL Certificate
Issues
Issues: Could not retrieve certificate details.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (ns2.afraid.org., kali.spacetechnology.net.); 3 MX records present. Issues: DNSSEC not configured — DNS responses can be spoofed; Zone transfer (AXFR) allowed on: kali.spacetechnology.net. — full zone data exposed.