Identity
8
F
withgoogle.com
Posture Score: 32/100
Scanned May 27, 2026 at 4:37 PM UTC
Attack Surface
0
Reputation
88
Identity Findings
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: 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.
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.
Subdomains have no DMARC enforcement
No sp= tag set and p=none. Subdomains inherit the monitoring-only policy, leaving them open to spoofing.
💡 Add sp=reject (or sp=quarantine) to your DMARC record to protect subdomains.
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.withgoogle.com
DMARC policy is monitoring-only (p=none)
The p=none policy only monitors; it does not instruct receivers to quarantine or reject unauthenticated mail.
💡 Upgrade to p=quarantine or p=reject after reviewing aggregate reports.
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.withgoogle.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.
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).
Void lookup: include:_spf.ip.bluestatedigital.com
The mechanism include:_spf.ip.bluestatedigital.com returns no records, wasting a DNS lookup.
💡 Remove mechanisms that reference non-existent domains.
Void lookup: include:_spf.a.bluestatedigital.com
The mechanism include:_spf.a.bluestatedigital.com returns no records, wasting a DNS lookup.
💡 Remove mechanisms that reference non-existent domains.
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@withgoogle.com").
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 length OK (129 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.
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
MX records are valid
All MX records are properly configured.
ARC support likely available
MX server software appears to support ARC headers for authentication preservation.
Meets bulk sender authentication requirements
Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.
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.
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.
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 smtp.google.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
MX IPs span 2 different /16 networks, providing good diversity.
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
Non-responsive IP for www.withgoogle.com: 2a00:1450:400b:c01::8d
The subdomain www.withgoogle.com resolves to 2a00:1450:400b:c01::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c01::8d is operational or remove the DNS record for www.withgoogle.com.
Non-responsive IP for ftp.withgoogle.com: 2a00:1450:400b:c01::8d
The subdomain ftp.withgoogle.com resolves to 2a00:1450:400b:c01::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c01::8d is operational or remove the DNS record for ftp.withgoogle.com.
Non-responsive IP for ns1.withgoogle.com: 2a00:1450:400b:c00::8d
The subdomain ns1.withgoogle.com resolves to 2a00:1450:400b:c00::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c00::8d is operational or remove the DNS record for ns1.withgoogle.com.
Non-responsive IP for ns2.withgoogle.com: 2a00:1450:400b:c02::8d
The subdomain ns2.withgoogle.com resolves to 2a00:1450:400b:c02::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c02::8d is operational or remove the DNS record for ns2.withgoogle.com.
Non-responsive IP for vpn.withgoogle.com: 2a00:1450:400b:c03::8d
The subdomain vpn.withgoogle.com resolves to 2a00:1450:400b:c03::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c03::8d is operational or remove the DNS record for vpn.withgoogle.com.
Non-responsive IP for remote.withgoogle.com: 2a00:1450:400b:c01::8d
The subdomain remote.withgoogle.com resolves to 2a00:1450:400b:c01::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c01::8d is operational or remove the DNS record for remote.withgoogle.com.
Non-responsive IP for admin.withgoogle.com: 2a00:1450:400b:c01::8d
The subdomain admin.withgoogle.com resolves to 2a00:1450:400b:c01::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c01::8d is operational or remove the DNS record for admin.withgoogle.com.
Non-responsive IP for portal.withgoogle.com: 2a00:1450:400b:c00::8d
The subdomain portal.withgoogle.com resolves to 2a00:1450:400b:c00::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c00::8d is operational or remove the DNS record for portal.withgoogle.com.
Non-responsive IP for dev.withgoogle.com: 2a00:1450:400b:c03::8d
The subdomain dev.withgoogle.com resolves to 2a00:1450:400b:c03::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c03::8d is operational or remove the DNS record for dev.withgoogle.com.
Non-responsive IP for staging.withgoogle.com: 2a00:1450:400b:c00::8d
The subdomain staging.withgoogle.com resolves to 2a00:1450:400b:c00::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c00::8d is operational or remove the DNS record for staging.withgoogle.com.
Non-responsive IP for test.withgoogle.com: 2a00:1450:400b:c00::8d
The subdomain test.withgoogle.com resolves to 2a00:1450:400b:c00::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c00::8d is operational or remove the DNS record for test.withgoogle.com.
Non-responsive IP for api.withgoogle.com: 2a00:1450:400b:c01::8d
The subdomain api.withgoogle.com resolves to 2a00:1450:400b:c01::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c01::8d is operational or remove the DNS record for api.withgoogle.com.
Non-responsive IP for app.withgoogle.com: 2a00:1450:400b:c00::8d
The subdomain app.withgoogle.com resolves to 2a00:1450:400b:c00::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c00::8d is operational or remove the DNS record for app.withgoogle.com.
Non-responsive IP for cdn.withgoogle.com: 2a00:1450:400b:c03::8d
The subdomain cdn.withgoogle.com resolves to 2a00:1450:400b:c03::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c03::8d is operational or remove the DNS record for cdn.withgoogle.com.
Non-responsive IP for blog.withgoogle.com: 2a00:1450:400b:c03::8d
The subdomain blog.withgoogle.com resolves to 2a00:1450:400b:c03::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c03::8d is operational or remove the DNS record for blog.withgoogle.com.
Non-responsive IP for shop.withgoogle.com: 2a00:1450:400b:c01::8d
The subdomain shop.withgoogle.com resolves to 2a00:1450:400b:c01::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c01::8d is operational or remove the DNS record for shop.withgoogle.com.
Non-responsive IP for store.withgoogle.com: 2a00:1450:400b:c01::8d
The subdomain store.withgoogle.com resolves to 2a00:1450:400b:c01::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c01::8d is operational or remove the DNS record for store.withgoogle.com.
Non-responsive IP for support.withgoogle.com: 2a00:1450:400b:c01::8d
The subdomain support.withgoogle.com resolves to 2a00:1450:400b:c01::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c01::8d is operational or remove the DNS record for support.withgoogle.com.
Non-responsive IP for help.withgoogle.com: 2a00:1450:400b:c01::8d
The subdomain help.withgoogle.com resolves to 2a00:1450:400b:c01::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c01::8d is operational or remove the DNS record for help.withgoogle.com.
Non-responsive IP for docs.withgoogle.com: 2a00:1450:400b:c02::8d
The subdomain docs.withgoogle.com resolves to 2a00:1450:400b:c02::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c02::8d is operational or remove the DNS record for docs.withgoogle.com.
Non-responsive IP for status.withgoogle.com: 2a00:1450:400b:c02::8d
The subdomain status.withgoogle.com resolves to 2a00:1450:400b:c02::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c02::8d is operational or remove the DNS record for status.withgoogle.com.
Non-responsive IP for git.withgoogle.com: 2a00:1450:400b:c00::8d
The subdomain git.withgoogle.com resolves to 2a00:1450:400b:c00::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c00::8d is operational or remove the DNS record for git.withgoogle.com.
Non-responsive IP for ci.withgoogle.com: 2a00:1450:400b:c01::8d
The subdomain ci.withgoogle.com resolves to 2a00:1450:400b:c01::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c01::8d is operational or remove the DNS record for ci.withgoogle.com.
Non-responsive IP for jenkins.withgoogle.com: 2a00:1450:400b:c00::8d
The subdomain jenkins.withgoogle.com resolves to 2a00:1450:400b:c00::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c00::8d is operational or remove the DNS record for jenkins.withgoogle.com.
Non-responsive IP for grafana.withgoogle.com: 2a00:1450:400b:c01::8d
The subdomain grafana.withgoogle.com resolves to 2a00:1450:400b:c01::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c01::8d is operational or remove the DNS record for grafana.withgoogle.com.
Non-responsive IP for prometheus.withgoogle.com: 2a00:1450:400b:c03::8d
The subdomain prometheus.withgoogle.com resolves to 2a00:1450:400b:c03::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c03::8d is operational or remove the DNS record for prometheus.withgoogle.com.
Non-responsive IP for kibana.withgoogle.com: 2a00:1450:400b:c00::8d
The subdomain kibana.withgoogle.com resolves to 2a00:1450:400b:c00::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c00::8d is operational or remove the DNS record for kibana.withgoogle.com.
Non-responsive IP for elastic.withgoogle.com: 2a00:1450:400b:c03::8d
The subdomain elastic.withgoogle.com resolves to 2a00:1450:400b:c03::8d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:1450:400b:c03::8d is operational or remove the DNS record for elastic.withgoogle.com.
DNS ANY query returns 23 record(s)
The DNS server responds to ANY queries with 23 record(s), creating significant DNS amplification risk.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
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.
25 subdomain(s) discovered for withgoogle.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 withgoogle.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.withgoogle.com, resolving to 209.85.203.141. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Microsoft Autodiscover endpoint detected
The Autodiscover endpoint at autodiscover.withgoogle.com responded with HTTP 404.
Reputation Findings
Missing Strict-Transport-Security on withgoogle.com
The Strict-Transport-Security header is not set on https://withgoogle.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.withgoogle.com
The Strict-Transport-Security header is not set on https://webmail.withgoogle.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
Wildcard MX records detected
Domain withgoogle.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.
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://withgoogle.com/.well-known/security.txt.
TLS certificate valid for 63 days
Certificate for withgoogle.com expires on 2026-07-30.
Certificate issued by WR2
The certificate for withgoogle.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for withgoogle.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for withgoogle.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for withgoogle.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on withgoogle.com.
Domain valid for 174 days
Domain withgoogle.com expires on 2026-11-17.
Domain transfer and delete locks enabled
Domain withgoogle.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for withgoogle.com do not match known disposable email provider patterns.
Domain is 6399 days old
Domain withgoogle.com was registered 2008-11-17.
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.
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
Strong TLS configuration on primary MX
Primary MX (smtp.google.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner from hosted mail provider
The MX (smtp.google.com) is a hosted mail service. Banner alignment is managed by the provider and not actionable by the domain owner.
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 registration data
Registrar: MarkMonitor Inc. | Created: 2008-11-17 | Expires: 2026-11-17 | Updated: 2025-10-16
WHOIS privacy protection not detected
Domain withgoogle.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: withgoogel.com (has MX!), witgoogle.com, withgogle.com, withgoole.com, withgoogl.com
5 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: none
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: none
⚠️ 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: smtp.google.com
PTR record proves mail server legitimacy
MX: smtp.google.com
Mail server at 74.125.193.27
→
PTR Record
Reverse DNS: di-in-f27.1e100.net
Mail Server Reputation: smtp.google.com
RBL check ensures server is not blacklisted
MX: smtp.google.com
Mail server at 74.125.193.27
→
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
MTA-STS not configured
⚠️ MTA-STS policy is missing. Even with TLS support, you lack the enforcement layer that prevents attackers from stripping encryption (downgrade attacks).
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
Mail servers support TLS encryption
→
TLS-RPT Reporting
TLS-RPT not configured
⚠️ TLS-RPT is not configured. Without TLS reporting, you have no visibility into TLS connection failures that may be impacting email delivery.
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/withgoogle.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan withgoogle.com Again