Identity
85
B
ginkgobioworks.com
Posture Score: 83/100
Scanned May 8, 2026 at 5:13 PM UTC
Attack Surface
80
Reputation
83
Identity Findings
No DKIM records found
No DKIM records were found for any common selector. Email may not be authenticated.
💡 Configure DKIM signing and publish the public key at <selector>._domainkey.ginkgobioworks.com
MTA-STS is in testing mode
The MTA-STS policy is in testing mode and not actively enforcing TLS.
💡 Switch mode to "enforce" once TLS is confirmed working for all MX hosts.
No CAA iodef tag configured
No iodef tag is present in the CAA records. CA policy violation reports will not be sent.
💡 Add an iodef CAA record. Example: 0 iodef "mailto:security@example.com"
Very low TTL on MX record: 287s
The MX record has a TTL of 287s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on TXT records: 287s
30 TXT records have a TTL of 287s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 287s
The SPF record has a TTL of 287s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on DMARC record: 287s
The DMARC record has a TTL of 287s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
NS TTL mismatch between parent and authoritative zone
The NS record TTL in the parent zone (~7187s) differs significantly from the authoritative zone (~86400s).
💡 Align NS record TTLs between the parent zone delegation and the authoritative zone.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
MX records are valid
All MX records are properly configured.
ARC support likely available
MX server software appears to support ARC headers for authentication preservation.
SMTP security checks passed
No open relay, VRFY/EXPN, or banner disclosure issues detected.
SMTP RFC 5321 compliance checks passed
The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.
IPv6 readiness is good
IPv6 records are present and properly configured.
STARTTLS downgrade resistance is adequate
STARTTLS is supported with modern TLS and protected by MTA-STS and/or DANE.
NS delegation is properly configured
All nameservers are responsive, consistent, and properly secured.
DNS responses are consistent across all nameservers
All authoritative nameservers return consistent answers with proper AA flags.
DKIM2 not detected
No DKIM key record with v=2 was found across common selectors. DKIM2 is an emerging standard and not yet widely deployed.
DMARC alignment: adkim=r, aspf=r
DKIM alignment is relaxed, SPF alignment is relaxed.
DMARCbis np tag absent
The DMARC record does not include the np (non-existent subdomain policy) tag. Consider adding np=reject to protect non-existent subdomains under DMARCbis.
DMARCbis psd tag absent
The DMARC record does not include the psd (public suffix domain) indicator. Consider adding psd=n to explicitly identify this as an organizational domain.
No DANE/TLSA records found
DANE is not configured for any MX server. This is optional but provides strong certificate binding.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open mail ports on smtp.google.com
Detected open mail-related ports: 25
RFC 8058 one-click unsubscribe assessment
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
MX IP network diversity
MX IPs span 3 different /16 networks, providing good diversity.
SOA record parameters
Serial: 2402707483, Refresh: 10000s, Retry: 2400s, Expire: 604800s, Min TTL: 1800s
Authorized certificate authorities
CAA records restrict certificate issuance to: globalsign.com, letsencrypt.org, pki.goog, sectigo.com
Attack Surface Findings
NSEC records enable zone walking
The domain uses NSEC records for DNSSEC authenticated denial of existence. NSEC records can be walked to enumerate all names in the zone, effectively disclosing the entire zone contents.
💡 Switch from NSEC to NSEC3 with opt-out to prevent zone enumeration. Use NSEC3 with a random salt and sufficient iterations.
Domain enumerability: high
The domain is highly enumerable. Zone transfers, NSEC zone walking, or a combination of factors make it easy to discover all DNS records.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
NSEC used instead of NSEC3 (zone enumeration possible)
The domain uses NSEC records for authenticated denial of existence. NSEC allows zone walking.
💡 Migrate from NSEC to NSEC3 to prevent zone enumeration.
No internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
2 subdomain(s) discovered for ginkgobioworks.com
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
0 certificate(s) found in CT logs
Certificate Transparency logs contain 0 certificate(s) for ginkgobioworks.com and its subdomains. Each certificate reveals subdomain names.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
Domain expires in 42 days
Domain ginkgobioworks.com expires on 2026-06-20 (42 days).
💡 Renew the domain registration soon — it expires within 60 days. Enable auto-renewal if available.
Missing domain locks: clientDeleteProhibited
Domain ginkgobioworks.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
HSTS enabled but missing preload directive on ginkgobioworks.com
Strict-Transport-Security: max-age=31536000
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
security.txt present
Found security.txt at https://ginkgobioworks.com/.well-known/security.txt.
TLS certificate valid for 75 days
Certificate for ginkgobioworks.com expires on 2026-07-23.
Certificate issued by R12
The certificate for ginkgobioworks.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for ginkgobioworks.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for ginkgobioworks.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for ginkgobioworks.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on ginkgobioworks.com.
Google Safe Browsing DNS check — no flag detected
DNS-based Safe Browsing lookup returned no results. Full verification requires the Google Safe Browsing API key.
Abuse contact lookup failed
Could not query abuse contact information.
PhishTank — API key required
PhishTank phishing database check requires an API key.
Sender Score — API key required
Sender Score reputation check requires an API key.
Cisco Talos — API key required
Cisco Talos IP reputation check requires an API key.
Could not connect to webmail.ginkgobioworks.com
HTTPS request to https://webmail.ginkgobioworks.com failed or timed out.
WHOIS registration data
Registrar: Cloudflare, Inc. | Created: 2008-06-20 | Expires: 2026-06-20 | Updated: 2025-05-21
WHOIS privacy protection enabled
Domain ginkgobioworks.com has WHOIS privacy/redaction enabled.
Dependency Chains
DMARC Authentication Chain (SPF)
DMARC uses SPF to verify that emails come from authorized servers
SPF Record
SPF record found and configured
→
DMARC Policy
DMARC policy: quarantine
DMARC Authentication Chain (DKIM)
DMARC uses DKIM to verify that emails have not been tampered with
DKIM Signature
DKIM signature missing
→
DMARC Policy
DMARC policy: quarantine
⚠️ DKIM signature is missing. DMARC relies on DKIM to verify email integrity and prevent tampering. Without DKIM, DMARC alignment will fail for cryptographic verification.
Mail Server Identity: smtp.google.com
PTR record proves mail server legitimacy
MX: smtp.google.com
Mail server at 209.85.203.27
→
PTR Record
Reverse DNS: dh-in-f27.1e100.net
Mail Server Reputation: smtp.google.com
RBL check ensures server is not blacklisted
MX: smtp.google.com
Mail server at 209.85.203.27
→
RBL Status
Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
Mail servers support TLS encryption
→
MTA-STS Policy
Mode: testing
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC policy: quarantine
→
BIMI Record
BIMI not configured
⚠️ BIMI record is missing. Even with DMARC enforcement, you need to configure BIMI to display your brand logo in supported email clients.
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
Mail servers support TLS encryption
→
TLS-RPT Reporting
TLS failure reporting configured
Security Checks
MX Records
✓
SPF Record
✓
DKIM Record
✗
DMARC Policy
✓
BIMI Record
✗
CAA Records
✗
DNSSEC
✓
MTA-STS
✓
TLS-RPT
✓
Embed Badge
Display your domain's security grade on your website or README:
<img src="https://scan.ractermx.com/badge/ginkgobioworks.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan ginkgobioworks.com Again