Identity
65
F
oligo.security
Posture Score: 50/100
Scanned May 8, 2026 at 4:49 PM UTC
Attack Surface
0
Reputation
84
Identity Findings
Open recursion on nameserver: ns-769.awsdns-32.net
The nameserver ns-769.awsdns-32.net allows recursive queries from external sources, making it vulnerable to DNS amplification attacks.
💡 Disable recursion on ns-769.awsdns-32.net or restrict it to trusted networks only.
Weak DKIM RSA key (~1296 bits) for selector 'google'
RSA keys shorter than 2048 bits are considered weak. Current key is approximately 1296 bits.
💡 Generate a new 2048-bit (or larger) RSA key pair and update the DKIM record.
No DMARC aggregate report URI (rua=)
Without rua=, you will not receive aggregate reports about authentication results.
💡 Add rua=mailto:dmarc-reports@oligo.security to your DMARC record.
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 TLS-RPT record found
Without TLS-RPT, you will not receive reports about TLS negotiation failures.
💡 Publish a _smtp._tls TXT record (e.g. "v=TLSRPTv1; rua=mailto:tls-reports@oligo.security").
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"
Slow DNS response from ns-295.awsdns-36.com: 2075.6ms
The nameserver ns-295.awsdns-36.com responded in 2075.6ms, exceeding the 500ms threshold.
💡 Investigate network latency or performance issues on ns-295.awsdns-36.com.
Very low TTL on MX records: 254s
5 MX records have a TTL of 254s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 255s
The SPF record has a TTL of 255s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on TXT record: 255s
The TXT record has a TTL of 255s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on DMARC record: 255s
The DMARC record has a TTL of 255s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
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).
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.
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.
Shared/free email hosting detected: aspmx.l.google.com
The MX record points to a known shared or free email hosting provider.
Shared/free email hosting detected: alt1.aspmx.l.google.com
The MX record points to a known shared or free email hosting provider.
Shared/free email hosting detected: alt2.aspmx.l.google.com
The MX record points to a known shared or free email hosting provider.
Shared/free email hosting detected: alt3.aspmx.l.google.com
The MX record points to a known shared or free email hosting provider.
Shared/free email hosting detected: alt4.aspmx.l.google.com
The MX record points to a known shared or free email hosting provider.
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 aspmx.l.google.com
Detected open mail-related ports: 25
RFC 8058 one-click unsubscribe assessment
DKIM signing is configured. RFC 8058 compliance depends on List-Unsubscribe and List-Unsubscribe-Post headers being included in outbound messages and DKIM signatures.
MX IP network diversity
MX IPs span 5 different /16 networks, providing good diversity.
SOA record parameters
Serial: 1, Refresh: 7200s, Retry: 900s, Expire: 1209600s, Min TTL: 300s
Authorized certificate authorities
CAA records restrict certificate issuance to: amazon.com, amazonaws.com, amazontrust.com, awstrust.com, godaddy.com, letsencrypt.org
Attack Surface Findings
Non-routable IPv4 in public DNS: mail.oligo.security → 10.100.130.179
The subdomain mail.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: mail.oligo.security → 10.100.195.139
The subdomain mail.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: mail.oligo.security → 10.100.189.157
The subdomain mail.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: ftp.oligo.security → 10.100.130.179
The subdomain ftp.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: ftp.oligo.security → 10.100.189.157
The subdomain ftp.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: ftp.oligo.security → 10.100.195.139
The subdomain ftp.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: smtp.oligo.security → 10.100.195.139
The subdomain smtp.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: smtp.oligo.security → 10.100.130.179
The subdomain smtp.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: smtp.oligo.security → 10.100.189.157
The subdomain smtp.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: pop.oligo.security → 10.100.189.157
The subdomain pop.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: pop.oligo.security → 10.100.195.139
The subdomain pop.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: pop.oligo.security → 10.100.130.179
The subdomain pop.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: imap.oligo.security → 10.100.189.157
The subdomain imap.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: imap.oligo.security → 10.100.195.139
The subdomain imap.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: imap.oligo.security → 10.100.130.179
The subdomain imap.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: webmail.oligo.security → 10.100.195.139
The subdomain webmail.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: webmail.oligo.security → 10.100.130.179
The subdomain webmail.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: webmail.oligo.security → 10.100.189.157
The subdomain webmail.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: mx.oligo.security → 10.100.195.139
The subdomain mx.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: mx.oligo.security → 10.100.189.157
The subdomain mx.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: mx.oligo.security → 10.100.130.179
The subdomain mx.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: ns1.oligo.security → 10.100.189.157
The subdomain ns1.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: ns1.oligo.security → 10.100.130.179
The subdomain ns1.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: ns1.oligo.security → 10.100.195.139
The subdomain ns1.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: ns2.oligo.security → 10.100.189.157
The subdomain ns2.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: ns2.oligo.security → 10.100.130.179
The subdomain ns2.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: ns2.oligo.security → 10.100.195.139
The subdomain ns2.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: vpn.oligo.security → 10.100.195.139
The subdomain vpn.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: vpn.oligo.security → 10.100.189.157
The subdomain vpn.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: vpn.oligo.security → 10.100.130.179
The subdomain vpn.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: remote.oligo.security → 10.100.195.139
The subdomain remote.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: remote.oligo.security → 10.100.130.179
The subdomain remote.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: remote.oligo.security → 10.100.189.157
The subdomain remote.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: admin.oligo.security → 10.100.173.118
The subdomain admin.oligo.security resolves to non-routable IP 10.100.173.118, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: admin.oligo.security → 10.100.195.11
The subdomain admin.oligo.security resolves to non-routable IP 10.100.195.11, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: portal.oligo.security → 10.100.189.157
The subdomain portal.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: portal.oligo.security → 10.100.195.139
The subdomain portal.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: portal.oligo.security → 10.100.130.179
The subdomain portal.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: staging.oligo.security → 10.100.195.139
The subdomain staging.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: staging.oligo.security → 10.100.189.157
The subdomain staging.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: staging.oligo.security → 10.100.130.179
The subdomain staging.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: test.oligo.security → 10.100.189.157
The subdomain test.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: test.oligo.security → 10.100.195.139
The subdomain test.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: test.oligo.security → 10.100.130.179
The subdomain test.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: api.oligo.security → 10.100.189.157
The subdomain api.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: api.oligo.security → 10.100.130.179
The subdomain api.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: api.oligo.security → 10.100.195.139
The subdomain api.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: cdn.oligo.security → 10.100.189.157
The subdomain cdn.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: cdn.oligo.security → 10.100.195.139
The subdomain cdn.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: cdn.oligo.security → 10.100.130.179
The subdomain cdn.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: blog.oligo.security → 10.100.130.179
The subdomain blog.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: blog.oligo.security → 10.100.189.157
The subdomain blog.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: blog.oligo.security → 10.100.195.139
The subdomain blog.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: shop.oligo.security → 10.100.195.139
The subdomain shop.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: shop.oligo.security → 10.100.130.179
The subdomain shop.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: shop.oligo.security → 10.100.189.157
The subdomain shop.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: store.oligo.security → 10.100.130.179
The subdomain store.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: store.oligo.security → 10.100.189.157
The subdomain store.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: store.oligo.security → 10.100.195.139
The subdomain store.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: help.oligo.security → 10.100.189.157
The subdomain help.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: help.oligo.security → 10.100.130.179
The subdomain help.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: help.oligo.security → 10.100.195.139
The subdomain help.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: status.oligo.security → 10.100.130.179
The subdomain status.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: status.oligo.security → 10.100.195.139
The subdomain status.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: status.oligo.security → 10.100.189.157
The subdomain status.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: git.oligo.security → 10.100.189.157
The subdomain git.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: git.oligo.security → 10.100.130.179
The subdomain git.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: git.oligo.security → 10.100.195.139
The subdomain git.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: ci.oligo.security → 10.100.189.157
The subdomain ci.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: ci.oligo.security → 10.100.130.179
The subdomain ci.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: ci.oligo.security → 10.100.195.139
The subdomain ci.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: jenkins.oligo.security → 10.100.130.179
The subdomain jenkins.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: jenkins.oligo.security → 10.100.195.139
The subdomain jenkins.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: jenkins.oligo.security → 10.100.189.157
The subdomain jenkins.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: grafana.oligo.security → 10.100.195.139
The subdomain grafana.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: grafana.oligo.security → 10.100.130.179
The subdomain grafana.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: grafana.oligo.security → 10.100.189.157
The subdomain grafana.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: prometheus.oligo.security → 10.100.130.179
The subdomain prometheus.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: prometheus.oligo.security → 10.100.189.157
The subdomain prometheus.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: prometheus.oligo.security → 10.100.195.139
The subdomain prometheus.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: kibana.oligo.security → 10.100.195.139
The subdomain kibana.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: kibana.oligo.security → 10.100.189.157
The subdomain kibana.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: kibana.oligo.security → 10.100.130.179
The subdomain kibana.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: elastic.oligo.security → 10.100.130.179
The subdomain elastic.oligo.security resolves to non-routable IP 10.100.130.179, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: elastic.oligo.security → 10.100.189.157
The subdomain elastic.oligo.security resolves to non-routable IP 10.100.189.157, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: elastic.oligo.security → 10.100.195.139
The subdomain elastic.oligo.security resolves to non-routable IP 10.100.195.139, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
DNS ANY query returns 22 record(s)
The DNS server responds to ANY queries with 22 record(s), creating significant DNS amplification risk.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
No NSEC/NSEC3 records found
Neither NSEC nor NSEC3 records were found. Authenticated denial of existence is not configured.
💡 Configure NSEC3 records for authenticated denial of existence while preventing zone enumeration.
Domain enumerability: low
The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
5 subdomain(s) discovered for oligo.security
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 oligo.security and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.oligo.security, resolving to 10.100.189.157, 10.100.130.179, 10.100.195.139. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
Domain expires in 60 days
Domain oligo.security expires on 2026-07-07 (60 days).
💡 Renew the domain registration soon — it expires within 60 days. Enable auto-renewal if available.
Missing domain locks: clientDeleteProhibited
Domain oligo.security is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
HSTS enabled with preload on oligo.security
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
security.txt present
Found security.txt at https://oligo.security/.well-known/security.txt.
TLS certificate valid for 40 days
Certificate for oligo.security expires on 2026-06-18.
Certificate issued by E7
The certificate for oligo.security is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha384
The certificate for oligo.security uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for oligo.security uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for oligo.security contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on oligo.security.
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.oligo.security
HTTPS request to https://webmail.oligo.security failed or timed out.
WHOIS registration data
Registrar: Namecheap | Created: 2022-07-07 | Expires: 2026-07-07 | Updated: 2025-07-01
WHOIS privacy protection not detected
Domain oligo.security does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.
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: reject
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: reject
⚠️ 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: aspmx.l.google.com
PTR record proves mail server legitimacy
MX: aspmx.l.google.com
Mail server at 74.125.193.26
→
PTR Record
Reverse DNS: ig-in-f26.1e100.net
Mail Server Identity: alt1.aspmx.l.google.com
PTR record proves mail server legitimacy
MX: alt1.aspmx.l.google.com
Mail server at 173.194.76.27
→
PTR Record
Reverse DNS: ws-in-f27.1e100.net
Mail Server Identity: alt2.aspmx.l.google.com
PTR record proves mail server legitimacy
MX: alt2.aspmx.l.google.com
Mail server at 142.250.102.26
→
PTR Record
Reverse DNS: rb-in-f26.1e100.net
Mail Server Identity: alt3.aspmx.l.google.com
PTR record proves mail server legitimacy
MX: alt3.aspmx.l.google.com
Mail server at 192.178.213.27
→
PTR Record
Reverse DNS: yugrqzs-in-f27.1e100.net
Mail Server Identity: alt4.aspmx.l.google.com
PTR record proves mail server legitimacy
MX: alt4.aspmx.l.google.com
Mail server at 142.251.127.26
→
PTR Record
Reverse DNS: lcfrai-in-f26.1e100.net
Mail Server Reputation: aspmx.l.google.com
RBL check ensures server is not blacklisted
MX: aspmx.l.google.com
Mail server at 74.125.193.26
→
RBL Status
Not blacklisted
Mail Server Reputation: alt1.aspmx.l.google.com
RBL check ensures server is not blacklisted
MX: alt1.aspmx.l.google.com
Mail server at 173.194.76.27
→
RBL Status
Not blacklisted
Mail Server Reputation: alt2.aspmx.l.google.com
RBL check ensures server is not blacklisted
MX: alt2.aspmx.l.google.com
Mail server at 142.250.102.26
→
RBL Status
Not blacklisted
Mail Server Reputation: alt3.aspmx.l.google.com
RBL check ensures server is not blacklisted
MX: alt3.aspmx.l.google.com
Mail server at 192.178.213.27
→
RBL Status
Not blacklisted
Mail Server Reputation: alt4.aspmx.l.google.com
RBL check ensures server is not blacklisted
MX: alt4.aspmx.l.google.com
Mail server at 142.251.127.26
→
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: reject
→
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-RPT not configured
⚠️ TLS-RPT is not configured. Without TLS reporting, you have no visibility into TLS connection failures that may be impacting email delivery.
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/oligo.security.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan oligo.security Again