← Back to Scanner

blackkite.com

Name: blackkite.com Email Security Posture Assessment
Creator: RacterMX

Posture Score: 83/100

Scanned May 8, 2026 at 4:46 PM UTC

Identity

Attack Surface

Reputation

Identity Findings

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.blackkite.com/.well-known/mta-sts.txt

medium

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.

medium

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@blackkite.com").

low

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"

low

Very low TTL on MX records: 283s

5 MX records have a TTL of 283s or less (below 300s).

💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.

low

Very low TTL on TXT records: 283s

14 TXT records have a TTL of 283s or less (below 300s).

💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.

low

Very low TTL on SPF record: 283s

The SPF record has a TTL of 283s or less (below 300s).

💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.

low

Very low TTL on DMARC record: 283s

The DMARC record has a TTL of 283s or less (below 300s).

💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.

low

NS TTL mismatch between parent and authoritative zone

The NS record TTL in the parent zone (~7183s) differs significantly from the authoritative zone (~86400s).

💡 Align NS record TTLs between the parent zone delegation and the authoritative zone.

low

SPF record is valid

The SPF record is properly configured with valid syntax and within lookup limits.

pass

DKIM records are valid

DKIM records found and validated for selectors: google

pass

DKIM cryptographic configuration is compliant

No RFC 8301 compliance issues detected in DKIM key configuration.

pass

ARC support likely available

MX server software appears to support ARC headers for authentication preservation.

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

IPv6 readiness is good

IPv6 records are present and properly configured.

pass

NS delegation is properly configured

All nameservers are responsive, consistent, and properly secured.

pass

DNS responses are consistent across all nameservers

All authoritative nameservers return consistent answers with proper AA flags.

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

DMARC failure reporting: fo=1:d:s

Failure reporting option: 1:d:s

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

Deprecated DMARCbis tags found: pct

The DMARC record contains tags deprecated in DMARCbis: pct. Consider removing these for forward compatibility.

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

Shared/free email hosting detected: aspmx.l.google.com

The MX record points to a known shared or free email hosting provider.

informational

Shared/free email hosting detected: alt1.aspmx.l.google.com

The MX record points to a known shared or free email hosting provider.

informational

Shared/free email hosting detected: alt2.aspmx.l.google.com

The MX record points to a known shared or free email hosting provider.

informational

Shared/free email hosting detected: alt3.aspmx.l.google.com

The MX record points to a known shared or free email hosting provider.

informational

Shared/free email hosting detected: alt4.aspmx.l.google.com

The MX record points to a known shared or free email hosting provider.

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

Open mail ports on aspmx.l.google.com

Detected open mail-related ports: 25

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

MX IP network diversity

MX IPs span 5 different /16 networks, providing good diversity.

informational

SOA record parameters

Serial: 2403705149, Refresh: 10000s, Retry: 2400s, Expire: 604800s, Min TTL: 1800s

informational

Authorized certificate authorities

CAA records restrict certificate issuance to: comodoca.com, digicert.com; cansignhttpexchanges=yes, letsencrypt.org, pki.goog; cansignhttpexchanges=yes, ssl.com

informational

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.

high

Domain enumerability: high

The domain is highly enumerable. Zone transfers, NSEC zone walking, or a combination of factors make it easy to discover all DNS records.

💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.

high

Non-responsive IP for www.blackkite.com: 2606:4700::6812:1b64

The subdomain www.blackkite.com resolves to 2606:4700::6812:1b64 which is not responding on ports 80 or 443. This may indicate a decommissioned server.

💡 Verify the server at 2606:4700::6812:1b64 is operational or remove the DNS record for www.blackkite.com.

medium

Non-responsive IP for www.blackkite.com: 2606:4700::6812:1a64

The subdomain www.blackkite.com resolves to 2606:4700::6812:1a64 which is not responding on ports 80 or 443. This may indicate a decommissioned server.

💡 Verify the server at 2606:4700::6812:1a64 is operational or remove the DNS record for www.blackkite.com.

medium

NSEC used instead of NSEC3 (zone enumeration possible)

The domain uses NSEC records for authenticated denial of existence. NSEC allows zone walking.

💡 Migrate from NSEC to NSEC3 to prevent zone enumeration.

medium

No internal information leakage detected

No non-routable IP addresses or internal references were found in public DNS records.

pass

No email autodiscovery endpoints detected

No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.

pass

24 subdomain(s) discovered for blackkite.com

Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.

informational

673 certificate(s) found in CT logs

Certificate Transparency logs contain 673 certificate(s) for blackkite.com and its subdomains. Each certificate reveals subdomain names.

informational

DNSSEC is enabled

DNSKEY and/or DS records are present, indicating DNSSEC is configured.

informational

Reputation Findings

Missing domain locks: clientDeleteProhibited

Domain blackkite.com is missing protective locks: clientDeleteProhibited.

💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.

high

HSTS enabled with preload on blackkite.com

Strict-Transport-Security: max-age=2592000; includeSubDomains; preload

pass

security.txt present

Found security.txt at https://blackkite.com/.well-known/security.txt.

pass

TLS certificate valid for 82 days

Certificate for blackkite.com expires on 2026-07-30.

pass

Certificate issued by E8

The certificate for blackkite.com is issued by a third-party CA.

pass

Signature algorithm: ecdsa-with-sha384

The certificate for blackkite.com uses an acceptable signature algorithm.

pass

ECC key: 256 bits

The certificate for blackkite.com uses an adequate ECC key of 256 bits.

pass

SCTs present in certificate

The certificate for blackkite.com contains Signed Certificate Timestamps.

pass

No weak ciphers detected

No known weak cipher suites detected on blackkite.com.

pass

Domain valid for 2784 days

Domain blackkite.com expires on 2033-12-21.

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.blackkite.com

HTTPS request to https://webmail.blackkite.com failed or timed out.

informational

WHOIS registration data

Registrar: Cloudflare, Inc. | Created: 1999-12-21 | Expires: 2033-12-21 | Updated: 2024-10-02

informational

WHOIS privacy protection enabled

Domain blackkite.com has WHOIS privacy/redaction enabled.

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: quarantine

DMARC Authentication Chain (DKIM)

DMARC uses DKIM to verify that emails have not been tampered with

DKIM Signature DKIM signature missing → DMARC Policy DMARC policy: quarantine

⚠️ DKIM signature is missing. DMARC relies on DKIM to verify email integrity and prevent tampering. Without DKIM, DMARC alignment will fail for cryptographic verification.

Mail Server Identity: 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.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