google.com — DNS Report
C
70%
34
Pass
6
Warnings
0
Failures
6
Info
46
Total
Processed in 1s
● 📋 Domain Registration
PASS| Registrar | MarkMonitor Inc. |
| Registrar ID | 292 |
| Registry | Verisign |
| Registry ID | 2138514_DOMAIN_COM-VRSN |
| Created | Sep 15, 1997 |
| Updated | Sep 09, 2019 |
| Expires | Sep 14, 2028 (766 days left) |
| DNSSEC | ✗ Unsigned |
| Status | client delete prohibited client transfer prohibited client update prohibited server delete prohibited server transfer prohibited server update prohibited |
| RDAP Nameservers | ns1.google.com ns2.google.com ns3.google.com ns4.google.com |
● 🌐 DNS Records
PASSSOA Records (1)
| Name | Value | TTL |
|---|---|---|
| google.com | ns1.google.com dns-admin.google.com 961355711 900 900 1800 60 | 60 |
NS Records (4)
| Name | Value | TTL |
|---|---|---|
| google.com | ns2.google.com | 345600 |
| google.com | ns1.google.com | 345600 |
| google.com | ns3.google.com | 345600 |
| google.com | ns4.google.com | 345600 |
A Records (1)
| Name | Value | TTL |
|---|---|---|
| google.com | 142.251.219.174 | 300 |
AAAA Records (1)
| Name | Value | TTL |
|---|---|---|
| google.com | 2607:f8b0:4005:819::200e | 300 |
MX Records (1)
| Name | Value | TTL |
|---|---|---|
| google.com | smtp.google.com | 300 |
TXT Records (15)
| Name | Value | TTL |
|---|---|---|
| google.com | google-site-verification=wD8N7i1JTNTkezJ49swvWW48f8_9xveREV4oB-0Hf5o | 300 |
| google.com | apple-domain-verification=30afIBcvSuDV2PLX | 300 |
| google.com | google-site-verification=TV9-DBe4R80X4v0M4U_bd_J9cpOJM0nikft0jAgjmsQ | 300 |
| google.com | docusign=05958488-4752-4ef2-95eb-aa7ba8a3bd0e | 300 |
| google.com | globalsign-smime-dv=CDYX+XFHUw2wml6/Gb8+59BsH31KzUr6c1l2BPvqKX8= | 300 |
| google.com | Z29vZ2xl | 300 |
| google.com | facebook-domain-verification=22rm551cu4k0ab0bxsw536tlds4h95 | 300 |
| google.com | v=spf1 include:_spf.google.com ~all | 300 |
| google.com | onetrust-domain-verification=0d477fe608074e6f9c12bca7826035cc | 300 |
| google.com | onetrust-domain-verification=6d685f1d41a94696ad7ef771f68993e0 | 300 |
| google.com | work-accounts-domain-verification=Tcj6JjIMZOw2KsSEw2Nt2rLae89tN6 | 300 |
| google.com | google-site-verification=4ibFUgB-wXLQ_S7vsXVomSTVamuOXBiVAzpR5IZ87D0 | 300 |
| google.com | MS=E4A68B9AB2BB9670BCE15412F62916164C0B20BB | 300 |
| google.com | docusign=1b0a6754-49b1-4db5-8540-d2c12664b289 | 300 |
| google.com | cisco-ci-domain-verification=47c38bc8c4b74b7233e9053220c1bbe76bcc1cd33c7acf7acd36cd6a5332004b | 300 |
CAA Records (1)
| Name | Value | TTL |
|---|---|---|
| google.com | 0 issue "pki.goog" | 86400 |
● 🔗 Parent Nameservers
PASS| Nameserver | IPv4 | IPv6 | Glue |
|---|---|---|---|
| ns4.google.com | 216.239.38.10 | 2001:4860:4802:38::a | Yes |
| ns2.google.com | 216.239.34.10 | 2001:4860:4802:34::a | Yes |
| ns1.google.com | 216.239.32.10 | 2001:4860:4802:32::a | Yes |
| ns3.google.com | 216.239.36.10 | 2001:4860:4802:36::a | Yes |
| ✓ | Nameservers Listed at Parent | The parent TLD nameserver has 4 nameserver(s) listed for google.com.ns2.google.com ns1.google.com ns3.google.com ns4.google.com |
| ✓ | Minimum Nameserver Count | 4 nameservers found. Good redundancy. |
| ✓ | Glue Record: ns4.google.com | Glue record found for ns4.google.com: 2001:4860:4802:38::a, 216.239.38.10 |
| ✓ | Public IP: ns4.google.com | Nameserver ns4.google.com has a public IP address. |
| ✓ | Glue Record: ns2.google.com | Glue record found for ns2.google.com: 2001:4860:4802:34::a, 216.239.34.10 |
| ✓ | Public IP: ns2.google.com | Nameserver ns2.google.com has a public IP address. |
| ✓ | Glue Record: ns1.google.com | Glue record found for ns1.google.com: 2001:4860:4802:32::a, 216.239.32.10 |
| ✓ | Public IP: ns1.google.com | Nameserver ns1.google.com has a public IP address. |
| ✓ | Glue Record: ns3.google.com | Glue record found for ns3.google.com: 2001:4860:4802:36::a, 216.239.36.10 |
| ✓ | Public IP: ns3.google.com | Nameserver ns3.google.com has a public IP address. |
| ✓ | Parent/Auth NS Consistency | The nameservers listed at the parent match those returned by the authoritative nameservers. |
● 🖥️ Authoritative Nameservers
WARNING| Nameserver | UDP | TCP | Auth | Recursion | IPv6 | Latency |
|---|---|---|---|---|---|---|
| ns1.google.com | ✓ | ✓ | ✓ | Open | ✓ | 32ms |
| ns2.google.com | ✓ | ✓ | ✓ | Open | ✓ | 31ms |
| ns3.google.com | ✓ | ✓ | ✓ | Open | ✓ | 35ms |
| ns4.google.com | ✓ | ✓ | ✓ | Open | ✓ | 39ms |
| ✓ | Authoritative Nameservers Found | Found 4 authoritative nameserver(s): ns2.google.com, ns4.google.com, ns3.google.com, ns1.google.com |
| ✓ | All Nameservers Respond | All authoritative nameservers are responding to DNS queries. |
| ✓ | UDP DNS (Port 53) | At least one nameserver is responding to UDP DNS queries on port 53. |
| ✓ | TCP DNS (Port 53) | TCP DNS queries are supported. Required for large responses and DNSSEC. |
| ✓ | Authoritative Response | At least one nameserver returns an authoritative (AA) response for the zone. |
| ⚠ | Open Recursion | One or more nameservers appear to answer recursive queries. Authoritative nameservers should not be open resolvers. |
| ✓ | Public IP Addresses | All nameservers have publicly routable IP addresses. |
| ✓ | IPv6 Support | At least one nameserver has an IPv6 (AAAA) address. |
| ✓ | NS Record Consistency | All authoritative nameservers return identical NS records. |
| ✓ | Multiple Network Diversity | Nameservers appear to be on different subnets/networks. Good resilience. |
● 📄 SOA Record
WARNING| Primary NS (MNAME) | ns1.google.com |
| Email (RNAME) | dns-admin.google.com |
| Serial | 961355711 |
| Refresh | 900 (15 min) |
| Retry | 900 (15 min) |
| Expire | 1800 (30 min) |
| Minimum TTL | 60 (1 min) |
| ✓ | SOA Record Exists | SOA record found for google.com. |
| ✓ | SOA MNAME | SOA MNAME (ns1.google.com) is listed as an authoritative nameserver. |
| ✓ | SOA RNAME | SOA contact email: dns-admin@google.com |
| ℹ | SOA Serial Format | SOA serial is 961355711. The recommended format is YYYYMMDDNN (e.g., 2024010101). |
| ⚠ | SOA Serial Consistency | Authoritative nameservers return different SOA serial numbers. Zone transfer may be in progress or a secondary is lagging. |
| ⚠ | SOA Refresh | SOA Refresh is 900 seconds. Values below 1200s are unusually low. |
| ⚠ | SOA Retry | SOA Retry (900s) is >= Refresh (900s). Retry should be less than Refresh. |
| ⚠ | SOA Expire | SOA Expire is 1800 seconds (0 days). RFC 1912 recommends 2-4 weeks. |
| ✓ | SOA Minimum TTL | SOA Minimum TTL (negative caching) is 60 seconds. |
● 📧 Mail Servers (MX)
WARNING| Priority | Hostname | IPv4 | IPv6 | PTR |
|---|---|---|---|---|
| 10 | smtp.google.com | 192.178.212.27, 173.194.42.27, 173.194.195.26, 192.178.212.26, 173.194.195.27 | 2607:f8b0:4001:c11::1a, 2607:f8b0:4001:c74::1b, 2607:f8b0:4001:c11::1b, 2607:f8b0:4001:c74::1a | yucbfsr-in-f27.1e100.net, yucbfwv-in-f27.1e100.net, iw-in-f26.1e100.net, yucbfsr-in-f26.1e100.net, iw-in-f27.1e100.net |
| ✓ | MX Records Exist | Found 1 MX record(s) for google.com. |
| ⚠ | MX Redundancy | Only one MX record found. A single mail server is a single point of failure. Consider adding a backup MX. |
| ✓ | MX Reverse DNS (PTR) | MX server(s) have PTR (reverse DNS) records. Many mail servers require rDNS for anti-spam. |
| ✓ | MX Consistency | All authoritative nameservers return consistent MX records. |
● 🌍 WWW / Web
INFO| Target | Type | IPs |
|---|---|---|
| www.google.com | A | 142.251.152.119, 142.251.157.119, 142.251.151.119, 142.251.154.119, 142.251.150.119, 142.251.153.119, 142.251.156.119, 142.251.155.119, 2001:4860:4828:7700::, 2001:4860:4827:7700::, 2001:4860:482d:7700::, 2001:4860:482a:7700::, 2001:4860:482b:7700::, 2001:4860:4829:7700::, 2001:4860:482c:7700::, 2001:4860:4826:7700:: |
| ✓ | WWW Record | www.google.com resolves to: 142.251.152.119, 142.251.157.119, 142.251.151.119, 142.251.154.119, 142.251.150.119, 142.251.153.119, 142.251.156.119, 142.251.155.119, 2001:4860:4828:7700::, 2001:4860:4827:7700::, 2001:4860:482d:7700::, 2001:4860:482a:7700::, 2001:4860:482b:7700::, 2001:4860:4829:7700::, 2001:4860:482c:7700::, 2001:4860:4826:7700:: |
| ℹ | WWW vs Apex IP | www.google.com and google.com resolve to different IP addresses. This is normal if they are intentionally served differently. |
● 🔒 DNSSEC
INFO| Enabled | No |
Chain of Trust
| Level | DS | DNSKEY | RRSIG | Status |
|---|---|---|---|---|
| . | — | ✓ | ✓ | PASS |
| com | ✓ | ✓ | ✓ | PASS |
| google.com | — | — | — | INFO |
| ℹ | DNSSEC Status | DNSSEC is not enabled for google.com. No DS or DNSKEY records found. |
● 🛡️ Email Security
INFOSPF (Sender Policy Framework)
| Record | v=spf1 include:_spf.google.com ~all |
| All Mechanism | ~all |
| DNS Lookups | 1 / 10 max |
DMARC (Domain-based Message Authentication)
| Record | v=DMARC1; p=reject; rua=mailto:mailauth-reports@google.com |
| Policy (p=) | reject |
| Aggregate Reports (rua) | mailto:mailauth-reports@google.com |
CAA (Certificate Authority Authorization)
| Flag | Tag | Value |
|---|---|---|
| 0 | issue | pki.goog |
| ✓ | SPF Record | SPF record found.v=spf1 include:_spf.google.com ~all |
| ℹ | SPF All Mechanism | SPF record uses '~all' (softfail). Non-listed senders will be marked but not rejected. Consider '-all' for strict enforcement. |
| ✓ | SPF DNS Lookup Count | SPF record uses approximately 1 DNS lookups (limit is 10). |
| ✓ | DMARC Record | DMARC record found.v=DMARC1; p=reject; rua=mailto:mailauth-reports@google.com |
| ✓ | DMARC Policy | DMARC policy is 'reject'. Failing emails will be rejected. Maximum protection. |
| ✓ | DMARC Reporting (rua) | Aggregate reports (rua) will be sent to: mailto:mailauth-reports@google.com |
| ✓ | CAA Records | CAA records found (1). Certificate issuance is restricted. |
| ℹ | CAA issuewild Tag | No 'issuewild' CAA tag. The 'issue' policy applies to wildcard certificates too, unless overridden. |
| ℹ | CAA iodef Tag | No 'iodef' CAA tag. Consider adding an iodef tag to receive reports of unauthorized certificate requests. |
● 📡 DNS Propagation
PASS| Status | Resolver | Location | Result | Latency |
|---|---|---|---|---|
| ✓ | Cloudflare (1.1.1.1) | US (Cloudflare) | 142.251.35.142 | 11ms |
| ✓ | Comodo Secure (8.26.56.26) | US (Comodo) | 142.251.218.14 | 20ms |
| ✓ | Cloudflare 2 (1.0.0.1) | US (Cloudflare) | 142.250.72.206 | 11ms |
| ✓ | Google Public DNS 2 (8.8.4.4) | US (Google) | 142.251.219.14 | 32ms |
| ✓ | Google Public DNS (8.8.8.8) | US (Google) | 142.251.219.14 | 33ms |
| ✓ | OpenDNS (208.67.222.222) | US (OpenDNS) | 142.251.219.14 | 34ms |
| ✓ | Quad9 (9.9.9.9) | US (Quad9) | 142.251.41.14 | 21ms |
| ✓ | Verisign (64.6.64.6) | US (Verisign) | 142.251.35.78 | 16ms |
| ✓ | OpenDNS 2 (208.67.220.220) | US (OpenDNS) | 142.251.219.14 | 31ms |
| ✓ | Yandex.DNS (77.88.8.8) | RU (Yandex) | 172.217.20.78 | 190ms |
● 🔄 Reverse DNS (PTR)
INFO| IP Address | PTR Record | Forward Match |
|---|---|---|
| 192.178.212.27 | yucbfsr-in-f27.1e100.net | ✗ No match |
| 173.194.42.27 | yucbfwv-in-f27.1e100.net | ✗ No match |
| 173.194.195.26 | iw-in-f26.1e100.net | ✗ No match |
| 192.178.212.26 | yucbfsr-in-f26.1e100.net | ✗ No match |
| 173.194.195.27 | iw-in-f27.1e100.net | ✗ No match |