Identity
10
D
googleblog.com
Posture Score: 63/100
Scanned May 27, 2026 at 6:04 PM UTC
Attack Surface
94
Reputation
86
Identity Findings
No MX records found
The domain has no MX records and cannot receive email.
💡 Publish MX records pointing to your mail server(s).
Open recursion on nameserver: ns4.google.com
The nameserver ns4.google.com allows recursive queries from external sources, making it vulnerable to DNS amplification attacks.
💡 Disable recursion on ns4.google.com or restrict it to trusted networks only.
Open recursion on nameserver: ns1.google.com
The nameserver ns1.google.com allows recursive queries from external sources, making it vulnerable to DNS amplification attacks.
💡 Disable recursion on ns1.google.com or restrict it to trusted networks only.
Open recursion on nameserver: ns3.google.com
The nameserver ns3.google.com allows recursive queries from external sources, making it vulnerable to DNS amplification attacks.
💡 Disable recursion on ns3.google.com or restrict it to trusted networks only.
Open recursion on nameserver: ns2.google.com
The nameserver ns2.google.com allows recursive queries from external sources, making it vulnerable to DNS amplification attacks.
💡 Disable recursion on ns2.google.com or restrict it to trusted networks only.
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.googleblog.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.googleblog.com/.well-known/mta-sts.txt
SOA expire value too short
The SOA expire value is 1800s (<604,800s / 7 days). Secondary nameservers may stop serving the zone prematurely.
💡 Increase the SOA expire value to at least 604800 seconds (7 days).
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@googleblog.com").
ARC check skipped — no MX records
Cannot assess ARC support without MX records.
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"
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (11 bytes)
SPF record is within safe DNS packet size limits.
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.
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
Meets bulk sender authentication requirements
Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.
IPv6 readiness is good
IPv6 records are present and properly configured.
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.
DMARC alignment: adkim=r, aspf=r
DKIM alignment is relaxed, SPF alignment is relaxed.
DMARCbis np tag absent
The DMARC record does not include the np (non-existent subdomain policy) tag. Consider adding np=reject to protect non-existent subdomains under DMARCbis.
DMARCbis psd tag absent
The DMARC record does not include the psd (public suffix domain) indicator. Consider adding psd=n to explicitly identify this as an organizational domain.
DANE check skipped — no MX records
Cannot check DANE/TLSA without MX records.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open relay check skipped — no MX records
Cannot test for open relay without MX records.
SMTP compliance check skipped — no MX records
Cannot test SMTP compliance without MX records.
Port exposure check skipped — no MX records
Cannot scan ports without MX records.
STARTTLS downgrade check skipped — no MX records
Cannot test STARTTLS without MX records.
RFC 8058 one-click unsubscribe assessment
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
FCrDNS check skipped — no MX records
Cannot perform FCrDNS without MX records.
SOA record parameters
Serial: 921356657, Refresh: 900s, Retry: 900s, Expire: 1800s, Min TTL: 60s
Authorized certificate authorities
CAA records restrict certificate issuance to: pki.goog
Attack Surface Findings
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.
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.
Domain enumerability: low
The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.
Non-mail domain correctly publishes SPF -all
This domain has no MX and publishes "v=spf1 -all", preventing spoofing.
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 googleblog.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 googleblog.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.googleblog.com, resolving to 74.125.193.132. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Microsoft Autodiscover endpoint detected
The Autodiscover endpoint at autodiscover.googleblog.com responded with HTTP 404.
Reputation Findings
Domain expires in 32 days
Domain googleblog.com expires on 2026-06-29 (32 days).
💡 Renew the domain registration soon — it expires within 60 days. Enable auto-renewal if available.
Wildcard MX records detected
Domain googleblog.com has wildcard MX records, which can be abused for spam or phishing.
💡 Remove wildcard MX records and configure explicit MX entries only for legitimate mail-handling subdomains.
HSTS enabled but missing preload directive on googleblog.com
Strict-Transport-Security: max-age=86400; includeSubDomains
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
HSTS enabled but missing preload directive on webmail.googleblog.com
Strict-Transport-Security: max-age=86400; includeSubDomains
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
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://googleblog.com/.well-known/security.txt.
TLS certificate valid for 63 days
Certificate for googleblog.com expires on 2026-07-30.
Certificate issued by WR2
The certificate for googleblog.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for googleblog.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for googleblog.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for googleblog.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on googleblog.com.
Domain transfer and delete locks enabled
Domain googleblog.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for googleblog.com do not match known disposable email provider patterns.
Domain is 8733 days old
Domain googleblog.com was registered 2002-06-29.
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.
No abuse contacts resolved
Could not resolve abuse contact information for MX IPs via abusix.org.
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 registration data
Registrar: MarkMonitor Inc. | Created: 2002-06-29 | Expires: 2026-06-29 | Updated: 2025-05-28
WHOIS privacy protection not detected
Domain googleblog.com does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.
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: googlelog.com (has MX!), hoogleblog.com (has MX!), boogleblog.com
3 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 configured
→
DMARC Policy
DMARC policy: reject
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 failure reporting 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/googleblog.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan googleblog.com Again