← Back to Scanner
F

oligo.security

Posture Score: 25/100

Scanned May 17, 2026 at 11:39 AM UTC

Score History

100 50 0 May 8 May 17

Identity

0

Attack Surface

0

Reputation

76

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.
critical
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.
high
MX hostname does not resolve:
The MX hostname has no A or AAAA records.
💡 Ensure the MX hostname resolves to a valid IP address.
high
MX hostname does not resolve:
The MX hostname has no A or AAAA records.
💡 Ensure the MX hostname resolves to a valid IP address.
high
MX hostname does not resolve:
The MX hostname has no A or AAAA records.
💡 Ensure the MX hostname resolves to a valid IP address.
high
MX hostname does not resolve:
The MX hostname has no A or AAAA records.
💡 Ensure the MX hostname resolves to a valid IP address.
high
MX hostname does not resolve:
The MX hostname has no A or AAAA records.
💡 Ensure the MX hostname resolves to a valid IP address.
high
No STARTTLS support on
The mail server does not support STARTTLS. All email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
high
No STARTTLS support on
The mail server does not support STARTTLS. All email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
high
No STARTTLS support on
The mail server does not support STARTTLS. All email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
high
No STARTTLS support on
The mail server does not support STARTTLS. All email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
high
No STARTTLS support on
The mail server does not support STARTTLS. All email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
high
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.
medium
No CAA records found
No CAA records are configured. Any certificate authority can issue certificates for this domain.
💡 Add CAA records to restrict certificate issuance. Example: 0 issue "letsencrypt.org"
medium
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.
low
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").
low
ARC support not detected
No evidence of ARC (Authenticated Received Chain) support on MX servers. Forwarded messages may lose authentication.
💡 Consider enabling ARC signing on your mail servers to preserve authentication through forwarding.
low
Slow DNS response from ns-295.awsdns-36.com: 2096ms
The nameserver ns-295.awsdns-36.com responded in 2096ms, exceeding the 500ms threshold.
💡 Investigate network latency or performance issues on ns-295.awsdns-36.com.
low
Very low TTL on MX records: 284s
5 MX records have a TTL of 284s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
low
Very low TTL on SPF record: 285s
The SPF record has a TTL of 285s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
low
Very low TTL on TXT record: 285s
The TXT record has a TTL of 285s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
low
Very low TTL on DMARC record: 284s
The DMARC record has a TTL of 284s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
low
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
pass
SPF record length OK (100 bytes)
SPF record is within safe DNS packet size limits.
pass
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
pass
DKIM key strength indicates modern key management
All DKIM keys use RSA-2048+ or Ed25519, consistent with current best practices.
pass
No external DMARC report destinations
All DMARC report URIs point to the same domain — no external authorization needed.
pass
Subdomains protected (sp=reject)
DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.
pass
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
pass
5 MX records with 5 unique IPs
Multiple MX records provide mail delivery redundancy.
pass
Meets bulk sender authentication requirements
Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.
pass
SMTP security checks passed
No open relay, VRFY/EXPN, or banner disclosure issues detected.
pass
SMTP RFC 5321 compliance checks passed
The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.
pass
Mail server port configuration is acceptable
No concerning port exposure detected.
pass
IPv6 readiness is good
IPv6 records are present and properly configured.
pass
FCrDNS checks passed
All MX server IPs have valid forward-confirmed reverse DNS.
pass
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.
informational
DMARC alignment: adkim=r, aspf=r
DKIM alignment is relaxed, SPF alignment is relaxed.
informational
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.
informational
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.
informational
REQUIRETLS not advertised
The primary MX does not advertise REQUIRETLS (RFC 8689). This is an emerging standard — MTA-STS and DANE provide adequate TLS enforcement for most deployments.
informational
No DANE/TLSA records found
DANE is not configured for any MX server. This is optional but provides strong certificate binding.
informational
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
informational
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.
informational
SOA record parameters
Serial: 1, Refresh: 7200s, Retry: 900s, Expire: 1209600s, Min TTL: 300s
informational

Attack Surface Findings

Non-routable IPv4 in public DNS: mail.oligo.security → 10.100.185.127
The subdomain mail.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: mail.oligo.security → 10.100.199.71
The subdomain mail.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: mail.oligo.security → 10.100.147.127
The subdomain mail.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: ftp.oligo.security → 10.100.185.127
The subdomain ftp.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: ftp.oligo.security → 10.100.147.127
The subdomain ftp.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: ftp.oligo.security → 10.100.199.71
The subdomain ftp.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: smtp.oligo.security → 10.100.147.127
The subdomain smtp.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: smtp.oligo.security → 10.100.185.127
The subdomain smtp.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: smtp.oligo.security → 10.100.199.71
The subdomain smtp.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: pop.oligo.security → 10.100.199.71
The subdomain pop.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: pop.oligo.security → 10.100.147.127
The subdomain pop.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: pop.oligo.security → 10.100.185.127
The subdomain pop.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: imap.oligo.security → 10.100.147.127
The subdomain imap.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: imap.oligo.security → 10.100.185.127
The subdomain imap.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: imap.oligo.security → 10.100.199.71
The subdomain imap.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: webmail.oligo.security → 10.100.147.127
The subdomain webmail.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: webmail.oligo.security → 10.100.199.71
The subdomain webmail.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: webmail.oligo.security → 10.100.185.127
The subdomain webmail.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: mx.oligo.security → 10.100.185.127
The subdomain mx.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: mx.oligo.security → 10.100.147.127
The subdomain mx.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: mx.oligo.security → 10.100.199.71
The subdomain mx.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: ns1.oligo.security → 10.100.147.127
The subdomain ns1.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: ns1.oligo.security → 10.100.185.127
The subdomain ns1.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: ns1.oligo.security → 10.100.199.71
The subdomain ns1.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: ns2.oligo.security → 10.100.185.127
The subdomain ns2.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: ns2.oligo.security → 10.100.147.127
The subdomain ns2.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: ns2.oligo.security → 10.100.199.71
The subdomain ns2.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: vpn.oligo.security → 10.100.185.127
The subdomain vpn.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: vpn.oligo.security → 10.100.147.127
The subdomain vpn.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: vpn.oligo.security → 10.100.199.71
The subdomain vpn.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: remote.oligo.security → 10.100.199.71
The subdomain remote.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: remote.oligo.security → 10.100.185.127
The subdomain remote.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: remote.oligo.security → 10.100.147.127
The subdomain remote.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
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.
high
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.
high
Non-routable IPv4 in public DNS: portal.oligo.security → 10.100.199.71
The subdomain portal.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: portal.oligo.security → 10.100.185.127
The subdomain portal.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: portal.oligo.security → 10.100.147.127
The subdomain portal.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: staging.oligo.security → 10.100.199.71
The subdomain staging.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: staging.oligo.security → 10.100.185.127
The subdomain staging.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: staging.oligo.security → 10.100.147.127
The subdomain staging.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: test.oligo.security → 10.100.185.127
The subdomain test.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: test.oligo.security → 10.100.199.71
The subdomain test.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: test.oligo.security → 10.100.147.127
The subdomain test.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: api.oligo.security → 10.100.199.71
The subdomain api.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: api.oligo.security → 10.100.147.127
The subdomain api.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: api.oligo.security → 10.100.185.127
The subdomain api.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: cdn.oligo.security → 10.100.147.127
The subdomain cdn.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: cdn.oligo.security → 10.100.185.127
The subdomain cdn.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: cdn.oligo.security → 10.100.199.71
The subdomain cdn.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: blog.oligo.security → 10.100.199.71
The subdomain blog.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: blog.oligo.security → 10.100.185.127
The subdomain blog.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: blog.oligo.security → 10.100.147.127
The subdomain blog.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: shop.oligo.security → 10.100.185.127
The subdomain shop.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: shop.oligo.security → 10.100.199.71
The subdomain shop.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: shop.oligo.security → 10.100.147.127
The subdomain shop.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: store.oligo.security → 10.100.147.127
The subdomain store.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: store.oligo.security → 10.100.199.71
The subdomain store.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: store.oligo.security → 10.100.185.127
The subdomain store.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: help.oligo.security → 10.100.185.127
The subdomain help.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: help.oligo.security → 10.100.147.127
The subdomain help.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: help.oligo.security → 10.100.199.71
The subdomain help.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: status.oligo.security → 10.100.199.71
The subdomain status.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: status.oligo.security → 10.100.185.127
The subdomain status.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: status.oligo.security → 10.100.147.127
The subdomain status.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: git.oligo.security → 10.100.147.127
The subdomain git.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: git.oligo.security → 10.100.199.71
The subdomain git.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: git.oligo.security → 10.100.185.127
The subdomain git.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: ci.oligo.security → 10.100.185.127
The subdomain ci.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: ci.oligo.security → 10.100.199.71
The subdomain ci.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: ci.oligo.security → 10.100.147.127
The subdomain ci.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: jenkins.oligo.security → 10.100.147.127
The subdomain jenkins.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: jenkins.oligo.security → 10.100.185.127
The subdomain jenkins.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: jenkins.oligo.security → 10.100.199.71
The subdomain jenkins.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: grafana.oligo.security → 10.100.147.127
The subdomain grafana.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: grafana.oligo.security → 10.100.199.71
The subdomain grafana.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: grafana.oligo.security → 10.100.185.127
The subdomain grafana.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: prometheus.oligo.security → 10.100.185.127
The subdomain prometheus.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: prometheus.oligo.security → 10.100.147.127
The subdomain prometheus.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: prometheus.oligo.security → 10.100.199.71
The subdomain prometheus.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: kibana.oligo.security → 10.100.185.127
The subdomain kibana.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: kibana.oligo.security → 10.100.147.127
The subdomain kibana.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: kibana.oligo.security → 10.100.199.71
The subdomain kibana.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: elastic.oligo.security → 10.100.147.127
The subdomain elastic.oligo.security resolves to non-routable IP 10.100.147.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: elastic.oligo.security → 10.100.199.71
The subdomain elastic.oligo.security resolves to non-routable IP 10.100.199.71, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: elastic.oligo.security → 10.100.185.127
The subdomain elastic.oligo.security resolves to non-routable IP 10.100.185.127, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
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.
medium
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.
medium
Domain enumerability: low
The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.
low
All MX records resolve correctly
No dangling MX records detected — all MX hostnames resolve to valid IP addresses.
pass
Explicit MX records present
The domain has explicit MX records — no implicit A-record fallback delivery.
pass
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
pass
5 subdomain(s) discovered for oligo.security
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
informational
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.
informational
Wildcard DNS record detected
A wildcard DNS record exists for *.oligo.security, resolving to 10.100.185.127, 10.100.199.71, 10.100.147.127. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
informational
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
informational

Reputation Findings

Domain expires in 51 days
Domain oligo.security expires on 2026-07-07 (51 days).
💡 Renew the domain registration soon — it expires within 60 days. Enable auto-renewal if available.
high
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.
high
SMTP banner mismatch: mx.google.com
The SMTP banner identifies as 'mx.google.com' but the MX hostname is 'aspmx.l.google.com' and PTR resolves to 'ig-in-f27.1e100.net'. Microsoft and other receivers flag this mismatch as suspicious infrastructure.
💡 Configure the SMTP server banner to match the MX hostname or PTR record (aspmx.l.google.com).
high
HSTS enabled with preload on oligo.security
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
pass
security.txt present
Found security.txt at https://oligo.security/.well-known/security.txt.
pass
TLS certificate valid for 31 days
Certificate for oligo.security expires on 2026-06-18.
pass
Certificate issued by E7
The certificate for oligo.security is issued by a third-party CA.
pass
Signature algorithm: ecdsa-with-sha384
The certificate for oligo.security uses an acceptable signature algorithm.
pass
ECC key: 256 bits
The certificate for oligo.security uses an adequate ECC key of 256 bits.
pass
SCTs present in certificate
The certificate for oligo.security contains Signed Certificate Timestamps.
pass
No weak ciphers detected
No known weak cipher suites detected on oligo.security.
pass
TLD has good reputation
The .security TLD is not on known abuse watchlists.
pass
DMARC reporting destinations look legitimate
DMARC rua/ruf addresses do not point to known URL shortener services.
pass
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
pass
Strong TLS configuration on primary MX
Primary MX (aspmx.l.google.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
pass
No registered typosquat domains detected
None of the common typosquat mutations of this domain appear to be registered by third parties.
pass
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.
informational
Abuse contact lookup failed
Could not query abuse contact information.
informational
PhishTank — API key required
PhishTank phishing database check requires an API key.
informational
Sender Score — API key required
Sender Score reputation check requires an API key.
informational
Cisco Talos — API key required
Cisco Talos IP reputation check requires an API key.
informational
Could not connect to webmail.oligo.security
HTTPS request to https://webmail.oligo.security failed or timed out.
informational
WHOIS registration data
Registrar: Namecheap | Created: 2022-07-07 | Expires: 2026-07-07 | Updated: 2025-07-01
informational
WHOIS privacy protection not detected
Domain oligo.security does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.
informational

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 configured → DMARC Policy DMARC policy: reject
Mail Server Identity: aspmx.l.google.com
PTR record proves mail server legitimacy
MX: aspmx.l.google.com Mail server at 74.125.193.27 → PTR Record Reverse DNS: ig-in-f27.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.26 → PTR Record Reverse DNS: yugrqzs-in-f26.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.27 → 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.26 → 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 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:

oligo.security Email Security Grade
<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