Identity
6
F
mookie1.com
Posture Score: 56/100
Scanned May 29, 2026 at 5:41 AM UTC
Attack Surface
77
Reputation
85
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 NS records found
No nameserver records could be retrieved for this domain.
💡 Ensure NS records are properly configured at your registrar and in your zone file.
MX hostname resolves via CNAME: optout.ib.mookie1.com.edgekey.net
MX records should not point to a CNAME (RFC 2181). This can cause delivery failures.
💡 Point the MX record directly to an A/AAAA record, not a CNAME.
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); SPF not published (recommended alongside DKIM)
💡 Publish SPF, DKIM, and DMARC records. Implement RFC 8058 one-click unsubscribe for marketing mail.
Cannot check DNS consistency — no NS records
No nameserver records could be retrieved for consistency checking.
💡 Ensure NS records are properly configured.
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.mookie1.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.mookie1.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.
Generic ISP PTR hostname: a2-19-176-154.deploy.static.akamaitechnologies.com
The PTR record for 2.19.176.154 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.mookie1.com
Generic ISP PTR hostname: a2-19-176-171.deploy.static.akamaitechnologies.com
The PTR record for 2.19.176.171 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.mookie1.com
Generic ISP PTR hostname: a2-19-176-171.deploy.static.akamaitechnologies.com
The PTR record for 2.19.176.171 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.mookie1.com
Generic ISP PTR hostname: a2-19-176-154.deploy.static.akamaitechnologies.com
The PTR record for 2.19.176.154 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.mookie1.com
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@mookie1.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.
IPv6 MX address not accepting SMTP: 2a02:26f0:9b00::213:b0c1
The MX server optout.ib.mookie1.com.edgekey.net has AAAA record 2a02:26f0:9b00::213:b0c1 but port 25 is not reachable.
💡 Ensure the mail server listens on IPv6 addresses.
IPv6 MX address not accepting SMTP: 2a02:26f0:9b00::213:b0da
The MX server optout.ib.mookie1.com.edgekey.net has AAAA record 2a02:26f0:9b00::213:b0da but port 25 is not reachable.
💡 Ensure the mail server listens on IPv6 addresses.
IPv6 MX address not accepting SMTP: 2a02:26f0:9b00::213:b0da
The MX server e103797.dscb.akamaiedge.net has AAAA record 2a02:26f0:9b00::213:b0da but port 25 is not reachable.
💡 Ensure the mail server listens on IPv6 addresses.
IPv6 MX address not accepting SMTP: 2a02:26f0:9b00::213:b0c1
The MX server e103797.dscb.akamaiedge.net has AAAA record 2a02:26f0:9b00::213:b0c1 but port 25 is not reachable.
💡 Ensure the mail server listens on IPv6 addresses.
Shared IP 2.19.176.154 used by multiple MX servers
The IP 2.19.176.154 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Shared IP 2.19.176.171 used by multiple MX servers
The IP 2.19.176.171 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
All external report destinations authorized
External DMARC report destinations have valid authorization records per RFC 7489 §7.1.
Subdomains protected (sp=reject)
DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.
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.
Mail server port configuration is acceptable
No concerning port exposure detected.
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.
DMARC alignment: adkim=r, aspf=r
DKIM alignment is relaxed, SPF alignment is relaxed.
DMARC failure reporting: fo=1
Failure reports generated when any authentication mechanism fails.
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.
Deprecated DMARCbis tags found: pct
The DMARC record contains tags deprecated in DMARCbis: pct. Consider removing these for forward compatibility.
DMARCbis psd tag absent
The DMARC record does not include the psd (public suffix domain) indicator. Consider adding psd=n to explicitly identify this as an organizational domain.
No DANE/TLSA records found
DANE is not configured for any MX server. This is optional but provides strong certificate binding.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
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: 1652186112, Refresh: 10800s, Retry: 3600s, Expire: 2419200s, Min TTL: 3600s
Attack Surface Findings
NSEC records enable zone walking
The domain uses NSEC records for DNSSEC authenticated denial of existence. NSEC records can be walked to enumerate all names in the zone, effectively disclosing the entire zone contents.
💡 Switch from NSEC to NSEC3 with opt-out to prevent zone enumeration. Use NSEC3 with a random salt and sufficient iterations.
Non-mail domain has no SPF record
This domain has no MX records (does not receive mail) but also has no SPF record. Without "v=spf1 -all", attackers can spoof this domain in phishing emails.
💡 Publish "v=spf1 -all" to explicitly declare this domain sends no mail.
HINFO record exposes system information
An HINFO record for mookie1.com reveals hardware/OS details: CPU=, OS=. This aids attacker reconnaissance.
💡 Remove the HINFO record from public DNS. HINFO records are rarely needed and expose unnecessary system details.
LOC record exposes geographic location
A LOC record for mookie1.com reveals the physical location of infrastructure. This aids targeted attacks.
💡 Remove the LOC record from public DNS unless geographic information is intentionally published.
No MX records — A-record fallback active
The domain has no MX records but has an A record. Per RFC 5321, mail servers will attempt delivery to the A record IP. This domain may be silently accepting mail without SPF/DKIM/DMARC protection.
💡 If this domain should not receive mail, publish a Null MX record (RFC 7505): "0 ." as the MX. If it should receive mail, add proper MX records.
RP record exposes responsible person
An RP (Responsible Person) record for mookie1.com reveals contact information: optout.ib.mookie1.com.edgekey.net.
e103797.dscb.akamaiedge.net.. This can be used for social engineering.
💡 Remove the RP record if the contact information is not intended to be public.
Domain enumerability: low
The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.
No internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
1 subdomain(s) discovered for mookie1.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 mookie1.com and its subdomains. Each certificate reveals subdomain names.
NSEC3 authenticated denial of existence
The domain uses NSEC3 with -1 iteration(s) and salt '-'.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
Could not retrieve TLS certificate
Failed to connect to mookie1.com:443 or retrieve the peer certificate.
💡 Ensure the domain has a valid TLS certificate installed and port 443 is accessible.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
No disposable email provider MX records
MX records for mookie1.com do not match known disposable email provider patterns.
No wildcard MX records
No wildcard MX records detected for mookie1.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
DMARC reporting destinations look legitimate
DMARC rua/ruf addresses do not point to known URL shortener services.
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.
Could not connect to mookie1.com
HTTPS request to https://mookie1.com failed or timed out.
Could not connect to webmail.mookie1.com
HTTPS request to https://webmail.mookie1.com failed or timed out.
WHOIS lookup failed
Could not retrieve WHOIS data for mookie1.com.
Could not determine domain age
WHOIS creation date could not be parsed for mookie1.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: mooke1.com, mookie.com
2 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 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: optout.ib.mookie1.com.edgekey.net
PTR record proves mail server legitimacy
MX: optout.ib.mookie1.com.edgekey.net
Mail server at e103797.dscb.akamaiedge.net
→
PTR Record
No PTR record
⚠️ Mail server optout.ib.mookie1.com.edgekey.net (e103797.dscb.akamaiedge.net) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: e103797.dscb.akamaiedge.net
PTR record proves mail server legitimacy
MX: e103797.dscb.akamaiedge.net
Mail server at 2.19.176.171
→
PTR Record
Reverse DNS: a2-19-176-171.deploy.static.akamaitechnologies.com
Mail Server Reputation: optout.ib.mookie1.com.edgekey.net
RBL check ensures server is not blacklisted
MX: optout.ib.mookie1.com.edgekey.net
Mail server at e103797.dscb.akamaiedge.net
→
RBL Status
Not blacklisted
Mail Server Reputation: e103797.dscb.akamaiedge.net
RBL check ensures server is not blacklisted
MX: e103797.dscb.akamaiedge.net
Mail server at 2.19.176.171
→
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 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
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/mookie1.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan mookie1.com Again