SurfaceMap › w › withgoogle.com

withgoogle.com

Checked 2026-10-22 11:31 UTC · first added 2026-10-21
✗Problems found Score 66 of 100

Domain & DNS

warn

24 passed 2 warn 0 failed

Areas

iRegistration iDelegation ✓Nameservers !SOA !DNSSEC iRecords

Problems

  • !
    Unusual SOA timers
    SOA · refresh 15m is outside 20m–1d; retry 15m should be shorter than refresh 15m; expire 30m is shorter than 7d; secondaries stop answering too soon when the primary is down; expire 30m must be longer than refresh + retry; negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 15m, retry 15m, expire 30m, negative TTL 1m.
    #23
  • !
    Not signed
    DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Recent checks

!

Full report

Domain & DNS report for withgoogle.com ›

Mail

fail

18 passed 6 warn 1 failed

Areas

!SPF ✗DMARC !DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • !
    4 of 10 DNS lookups, with problems
    SPF · SPF record needs 4 DNS lookups (limit is 10). Problems found: include:_spf.ip.bluestatedigital.com does not exist or has no records; include:_spf.a.bluestatedigital.com does not exist or has no records.
    #2
  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    2 void lookups
    SPF · 2 include/redirect targets does not exist or has no records (limit is 2). This usually is a stale include; remove it.
    #26
  • !
    Not configured
    TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32

Recent checks

✗

Full report

Mail report for withgoogle.com ›