Identity
44
F
okxxx1.com
Posture Score: 45/100
Scanned May 28, 2026 at 12:48 AM UTC
Attack Surface
0
Reputation
92
Identity Findings
No SPF record found
The domain has no SPF record, allowing anyone to send email as this domain.
💡 Publish an SPF TXT record (e.g. "v=spf1 include:_spf.google.com -all").
No DMARC record found
The domain has no DMARC record, providing no policy for handling unauthenticated email.
💡 Publish a DMARC TXT record at _dmarc.okxxx1.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@okxxx1.com").
Does not meet bulk sender requirements
Google and Yahoo require all bulk senders to have SPF+DKIM, DMARC, and one-click unsubscribe. Issues: Neither SPF nor DKIM is configured (at least one required); No DMARC record published (required since Feb 2024); SPF not published (recommended alongside DKIM)
💡 Publish SPF, DKIM, and DMARC records. Implement RFC 8058 one-click unsubscribe for marketing mail.
No DKIM records found
No DKIM records were found after probing 56 common selectors. The domain may use a custom selector not discoverable via external scan.
💡 Configure DKIM signing and publish the public key at <selector>._domainkey.okxxx1.com
No MTA-STS record found
Without MTA-STS, mail transport encryption cannot be enforced and is vulnerable to downgrade attacks.
💡 Publish a _mta-sts TXT record and host a policy file at https://mta-sts.okxxx1.com/.well-known/mta-sts.txt
STARTTLS without MTA-STS or DANE protection
STARTTLS alone is vulnerable to downgrade attacks. Neither MTA-STS nor DANE is configured to enforce encryption.
💡 Deploy MTA-STS and/or DANE to protect against STARTTLS stripping attacks.
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"
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@okxxx1.com").
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.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
MX records are valid
All MX records are properly configured.
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.
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.
DNS TTL values follow best practices
All critical DNS record TTLs are within recommended ranges.
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.
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.
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 mx1.privatehost.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
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 2401708773, Refresh: 10000s, Retry: 2400s, Expire: 604800s, Min TTL: 1800s
Attack Surface Findings
Non-responsive IP for www.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain www.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for www.okxxx1.com.
Non-responsive IP for www.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain www.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for www.okxxx1.com.
Non-responsive IP for www.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain www.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for www.okxxx1.com.
Non-responsive IP for ftp.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain ftp.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for ftp.okxxx1.com.
Non-responsive IP for ftp.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain ftp.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for ftp.okxxx1.com.
Non-responsive IP for ftp.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain ftp.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for ftp.okxxx1.com.
Non-responsive IP for ns1.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain ns1.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for ns1.okxxx1.com.
Non-responsive IP for ns1.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain ns1.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for ns1.okxxx1.com.
Non-responsive IP for ns1.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain ns1.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for ns1.okxxx1.com.
Non-responsive IP for ns2.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain ns2.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for ns2.okxxx1.com.
Non-responsive IP for ns2.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain ns2.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for ns2.okxxx1.com.
Non-responsive IP for ns2.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain ns2.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for ns2.okxxx1.com.
Non-responsive IP for vpn.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain vpn.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for vpn.okxxx1.com.
Non-responsive IP for vpn.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain vpn.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for vpn.okxxx1.com.
Non-responsive IP for vpn.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain vpn.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for vpn.okxxx1.com.
Non-responsive IP for remote.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain remote.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for remote.okxxx1.com.
Non-responsive IP for remote.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain remote.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for remote.okxxx1.com.
Non-responsive IP for remote.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain remote.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for remote.okxxx1.com.
Non-responsive IP for admin.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain admin.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for admin.okxxx1.com.
Non-responsive IP for admin.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain admin.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for admin.okxxx1.com.
Non-responsive IP for admin.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain admin.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for admin.okxxx1.com.
Non-responsive IP for portal.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain portal.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for portal.okxxx1.com.
Non-responsive IP for portal.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain portal.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for portal.okxxx1.com.
Non-responsive IP for portal.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain portal.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for portal.okxxx1.com.
Non-responsive IP for dev.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain dev.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for dev.okxxx1.com.
Non-responsive IP for dev.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain dev.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for dev.okxxx1.com.
Non-responsive IP for dev.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain dev.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for dev.okxxx1.com.
Non-responsive IP for staging.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain staging.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for staging.okxxx1.com.
Non-responsive IP for staging.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain staging.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for staging.okxxx1.com.
Non-responsive IP for staging.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain staging.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for staging.okxxx1.com.
Non-responsive IP for test.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain test.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for test.okxxx1.com.
Non-responsive IP for test.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain test.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for test.okxxx1.com.
Non-responsive IP for test.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain test.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for test.okxxx1.com.
Non-responsive IP for api.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain api.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for api.okxxx1.com.
Non-responsive IP for api.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain api.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for api.okxxx1.com.
Non-responsive IP for api.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain api.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for api.okxxx1.com.
Non-responsive IP for app.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain app.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for app.okxxx1.com.
Non-responsive IP for app.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain app.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for app.okxxx1.com.
Non-responsive IP for app.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain app.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for app.okxxx1.com.
Non-responsive IP for cdn.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain cdn.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for cdn.okxxx1.com.
Non-responsive IP for cdn.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain cdn.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for cdn.okxxx1.com.
Non-responsive IP for cdn.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain cdn.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for cdn.okxxx1.com.
Non-responsive IP for blog.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain blog.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for blog.okxxx1.com.
Non-responsive IP for blog.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain blog.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for blog.okxxx1.com.
Non-responsive IP for blog.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain blog.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for blog.okxxx1.com.
Non-responsive IP for shop.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain shop.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for shop.okxxx1.com.
Non-responsive IP for shop.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain shop.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for shop.okxxx1.com.
Non-responsive IP for shop.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain shop.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for shop.okxxx1.com.
Non-responsive IP for store.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain store.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for store.okxxx1.com.
Non-responsive IP for store.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain store.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for store.okxxx1.com.
Non-responsive IP for store.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain store.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for store.okxxx1.com.
Non-responsive IP for support.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain support.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for support.okxxx1.com.
Non-responsive IP for support.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain support.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for support.okxxx1.com.
Non-responsive IP for support.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain support.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for support.okxxx1.com.
Non-responsive IP for help.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain help.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for help.okxxx1.com.
Non-responsive IP for help.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain help.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for help.okxxx1.com.
Non-responsive IP for help.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain help.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for help.okxxx1.com.
Non-responsive IP for docs.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain docs.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for docs.okxxx1.com.
Non-responsive IP for docs.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain docs.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for docs.okxxx1.com.
Non-responsive IP for docs.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain docs.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for docs.okxxx1.com.
Non-responsive IP for status.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain status.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for status.okxxx1.com.
Non-responsive IP for status.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain status.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for status.okxxx1.com.
Non-responsive IP for status.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain status.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for status.okxxx1.com.
Non-responsive IP for git.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain git.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for git.okxxx1.com.
Non-responsive IP for git.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain git.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for git.okxxx1.com.
Non-responsive IP for git.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain git.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for git.okxxx1.com.
Non-responsive IP for ci.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain ci.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for ci.okxxx1.com.
Non-responsive IP for ci.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain ci.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for ci.okxxx1.com.
Non-responsive IP for ci.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain ci.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for ci.okxxx1.com.
Non-responsive IP for jenkins.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain jenkins.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for jenkins.okxxx1.com.
Non-responsive IP for jenkins.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain jenkins.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for jenkins.okxxx1.com.
Non-responsive IP for jenkins.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain jenkins.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for jenkins.okxxx1.com.
Non-responsive IP for grafana.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain grafana.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for grafana.okxxx1.com.
Non-responsive IP for grafana.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain grafana.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for grafana.okxxx1.com.
Non-responsive IP for grafana.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain grafana.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for grafana.okxxx1.com.
Non-responsive IP for prometheus.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain prometheus.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for prometheus.okxxx1.com.
Non-responsive IP for prometheus.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain prometheus.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for prometheus.okxxx1.com.
Non-responsive IP for prometheus.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain prometheus.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for prometheus.okxxx1.com.
Non-responsive IP for kibana.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain kibana.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for kibana.okxxx1.com.
Non-responsive IP for kibana.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain kibana.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for kibana.okxxx1.com.
Non-responsive IP for kibana.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain kibana.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for kibana.okxxx1.com.
Non-responsive IP for elastic.okxxx1.com: 2606:4700:20::681a:4b0
The subdomain elastic.okxxx1.com resolves to 2606:4700:20::681a:4b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:4b0 is operational or remove the DNS record for elastic.okxxx1.com.
Non-responsive IP for elastic.okxxx1.com: 2606:4700:20::681a:5b0
The subdomain elastic.okxxx1.com resolves to 2606:4700:20::681a:5b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::681a:5b0 is operational or remove the DNS record for elastic.okxxx1.com.
Non-responsive IP for elastic.okxxx1.com: 2606:4700:20::ac43:44b7
The subdomain elastic.okxxx1.com resolves to 2606:4700:20::ac43:44b7 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:20::ac43:44b7 is operational or remove the DNS record for elastic.okxxx1.com.
DNSSEC is not enabled
No DNSKEY or DS records were found. DNS responses are not cryptographically authenticated.
💡 Enable DNSSEC by generating DNSKEY records and publishing DS records at the registrar.
Domain enumerability: low
The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.
All MX records resolve correctly
No dangling MX records detected — all MX hostnames resolve to valid IP addresses.
Explicit MX records present
The domain has explicit MX records — no implicit A-record fallback delivery.
No internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
No excessive DNS information exposure detected
No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.
0 subdomain(s) discovered for okxxx1.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 okxxx1.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.okxxx1.com, resolving to 104.26.5.176, 172.67.68.183, 104.26.4.176. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Microsoft Autodiscover endpoint detected
The Autodiscover endpoint at autodiscover.okxxx1.com responded with HTTP 404.
Reputation Findings
Missing Strict-Transport-Security on okxxx1.com
The Strict-Transport-Security header is not set on https://okxxx1.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
Missing Strict-Transport-Security on webmail.okxxx1.com
The Strict-Transport-Security header is not set on https://webmail.okxxx1.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
security.txt present
Found security.txt at https://okxxx1.com/.well-known/security.txt.
TLS certificate valid for 33 days
Certificate for okxxx1.com expires on 2026-06-30.
Certificate issued by WE1
The certificate for okxxx1.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha256
The certificate for okxxx1.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for okxxx1.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for okxxx1.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on okxxx1.com.
No disposable email provider MX records
MX records for okxxx1.com do not match known disposable email provider patterns.
No wildcard MX records
No wildcard MX records detected for okxxx1.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
Strong TLS configuration on primary MX
Primary MX (mx1.privatehost.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner matches infrastructure identity
The SMTP banner (mx1.privatehost.com) aligns with the MX hostname (mx1.privatehost.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 contacts found for MX IPs
Abuse contact information retrieved via abusix.org DNS lookup.
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.
WHOIS lookup failed
Could not retrieve WHOIS data for okxxx1.com.
Could not determine domain age
WHOIS creation date could not be parsed for okxxx1.com.
Bulletproof Hosting Detection — API key required
Checking IPs against known bulletproof hosting providers requires a threat intelligence API key.
Threat Intelligence Feeds — API key required
Checking domain against threat intelligence feeds requires API keys (e.g., VirusTotal, AbuseIPDB).
Typosquat detected: okxxx.com (has MX!)
1 registered lookalike domain(s) that could be used for phishing against your brand. Domains with MX records can send and receive email, making them high-risk phishing vectors.
Dependency Chains
DMARC Authentication Chain (SPF)
DMARC uses SPF to verify that emails come from authorized servers
SPF Record
SPF record missing
→
DMARC Policy
DMARC policy missing
⚠️ SPF record is missing. DMARC relies on SPF to verify sender authorization. Without SPF, DMARC alignment will fail, reducing email deliverability and brand protection.
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 missing
⚠️ 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: mx1.privatehost.com
PTR record proves mail server legitimacy
MX: mx1.privatehost.com
Mail server at 185.75.76.9
→
PTR Record
Reverse DNS: mx1.privatehost.com
Mail Server Reputation: mx1.privatehost.com
RBL check ensures server is not blacklisted
MX: mx1.privatehost.com
Mail server at 185.75.76.9
→
RBL Status
Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
TLS not verified or unsupported
→
MTA-STS Policy
MTA-STS not configured
⚠️ TLS support could not be verified. MTA-STS requires TLS to enforce encrypted connections. Without TLS, MTA-STS cannot function.
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC not enforced (p=none or missing)
→
BIMI Record
BIMI not configured
⚠️ DMARC is not enforced. BIMI requires a DMARC policy of "quarantine" or "reject" to prove you have strong email authentication. Without enforcement, email clients will not display your logo.
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
TLS not verified or unsupported
→
TLS-RPT Reporting
TLS-RPT not configured
⚠️ TLS support could not be verified. TLS-RPT reports on TLS connection failures, but without TLS support, there's nothing to monitor. You need working TLS encryption before TLS-RPT can provide value.
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/okxxx1.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan okxxx1.com Again