google.cz — DNS Report
C
73%
32
Pass
5
Warnings
0
Failures
5
Info
42
Total
Processed in 1s
● 📋 Domain Registration
PASS| Registrar | REG-MARKMONITOR |
| Registrant | MM1171195 |
| WHOIS Server | whois.nic.cz |
| RDAP Nameservers | ns2.google.com ns4.google.com ns3.google.com ns1.google.com |
● 🌐 DNS Records
PASSSOA Records (1)
| Name | Value | TTL |
|---|---|---|
| google.cz | ns1.google.com dns-admin.google.com 965142848 900 900 1800 60 | 60 |
NS Records (4)
| Name | Value | TTL |
|---|---|---|
| google.cz | ns4.google.com | 345600 |
| google.cz | ns1.google.com | 345600 |
| google.cz | ns3.google.com | 345600 |
| google.cz | ns2.google.com | 345600 |
A Records (1)
| Name | Value | TTL |
|---|---|---|
| google.cz | 142.251.218.195 | 300 |
AAAA Records (1)
| Name | Value | TTL |
|---|---|---|
| google.cz | 2607:f8b0:4005:80b::2003 | 300 |
MX Records (1)
| Name | Value | TTL |
|---|---|---|
| google.cz | smtp.google.com | 300 |
TXT Records (1)
| Name | Value | TTL |
|---|---|---|
| google.cz | v=spf1 -all | 300 |
CAA Records (1)
| Name | Value | TTL |
|---|---|---|
| google.cz | 0 issue "pki.goog" | 86400 |
● 🔗 Parent Nameservers
PASS| Nameserver | IPv4 | IPv6 | Glue |
|---|---|---|---|
| ns2.google.com | 216.239.34.10 | 2001:4860:4802:34::a | No |
| ns4.google.com | 216.239.38.10 | 2001:4860:4802:38::a | No |
| ns3.google.com | 216.239.36.10 | 2001:4860:4802:36::a | No |
| ns1.google.com | 216.239.32.10 | 2001:4860:4802:32::a | No |
| ✓ | Nameservers Listed at Parent | The parent TLD nameserver has 4 nameserver(s) listed for google.cz.ns1.google.com ns2.google.com ns3.google.com ns4.google.com |
| ✓ | Minimum Nameserver Count | 4 nameservers found. Good redundancy. |
| ✓ | Public IP: ns2.google.com | Nameserver ns2.google.com has a public IP address. |
| ✓ | Public IP: ns4.google.com | Nameserver ns4.google.com has a public IP address. |
| ✓ | Public IP: ns3.google.com | Nameserver ns3.google.com has a public IP address. |
| ✓ | Public IP: ns1.google.com | Nameserver ns1.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 | ✓ | 36ms |
| ns4.google.com | ✓ | ✓ | ✓ | Open | ✓ | 40ms |
| ✓ | Authoritative Nameservers Found | Found 4 authoritative nameserver(s): ns4.google.com, ns3.google.com, ns2.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 | 965142848 |
| 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.cz. |
| ✓ | 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 965142848. The recommended format is YYYYMMDDNN (e.g., 2024010101). |
| ✓ | SOA Serial Consistency | All authoritative nameservers return the same SOA serial number. |
| ⚠ | 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 |
|---|---|---|---|---|
| 0 | smtp.google.com | 192.178.210.27, 192.178.210.26, 74.125.126.26, 74.125.126.27, 192.178.129.26 | 2607:f8b0:4001:c72::1a, 2607:f8b0:4001:c1d::1b, 2607:f8b0:4001:c1d::1a, 2607:f8b0:4001:c72::1b | yucbfiv-in-f27.1e100.net, yucbfiv-in-f26.1e100.net, ik-in-f26.1e100.net, ik-in-f27.1e100.net, yucbflq-in-f26.1e100.net |
| ✓ | MX Records Exist | Found 1 MX record(s) for google.cz. |
| ⚠ | 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.cz | A | 142.251.219.3, 2607:f8b0:4005:816::2003 |
| ✓ | WWW Record | www.google.cz resolves to: 142.251.219.3, 2607:f8b0:4005:816::2003 |
| ℹ | WWW vs Apex IP | www.google.cz and google.cz 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 |
| cz | ✓ | ✓ | ✓ | PASS |
| google.cz | — | — | — | INFO |
| ℹ | DNSSEC Status | DNSSEC is not enabled for google.cz. No DS or DNSKEY records found. |
● 🛡️ Email Security
INFOSPF (Sender Policy Framework)
| Record | v=spf1 -all |
| All Mechanism | -all |
| DNS Lookups | 0 / 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 -all |
| ✓ | SPF All Mechanism | SPF record uses '-all' (fail). Non-listed senders will be rejected. Good. |
| ✓ | SPF DNS Lookup Count | SPF record uses approximately 0 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 2 (1.0.0.1) | US (Cloudflare) | 142.251.35.131 | 23ms |
| ✓ | Quad9 (9.9.9.9) | US (Quad9) | 142.251.214.99 | 28ms |
| ✓ | OpenDNS (208.67.222.222) | US (OpenDNS) | 142.251.218.67 | 34ms |
| ✓ | OpenDNS 2 (208.67.220.220) | US (OpenDNS) | 142.251.218.67 | 40ms |
| ✓ | Verisign (64.6.64.6) | US (Verisign) | 142.251.215.227 | 32ms |
| ✓ | Comodo Secure (8.26.56.26) | US (Comodo) | 142.251.35.67 | 61ms |
| ✓ | Google Public DNS (8.8.8.8) | US (Google) | 142.251.218.67 | 32ms |
| ✓ | Cloudflare (1.1.1.1) | US (Cloudflare) | 142.250.188.35 | 23ms |
| ✓ | Google Public DNS 2 (8.8.4.4) | US (Google) | 142.251.218.67 | 40ms |
| ✓ | Yandex.DNS (77.88.8.8) | RU (Yandex) | 172.217.20.67 | 204ms |
● 🔄 Reverse DNS (PTR)
INFO| IP Address | PTR Record | Forward Match |
|---|---|---|
| 192.178.210.27 | yucbfiv-in-f27.1e100.net | ✗ No match |
| 192.178.210.26 | yucbfiv-in-f26.1e100.net | ✗ No match |
| 74.125.126.26 | ik-in-f26.1e100.net | ✗ No match |
| 74.125.126.27 | ik-in-f27.1e100.net | ✗ No match |
| 192.178.129.26 | yucbflq-in-f26.1e100.net | ✗ No match |