google.je — DNS Report

Scan ID: google.je-1786881072442360415 Scanned: Aug 16, 2026

D 66%

Rescan

31 Pass

6 Warnings

1 Failures

5 Info

43 Total

Processed in 1s

● 📋 Domain Registration

PASS

Registrar	MarkMonitor Inc. (http://www.markmonitor.com)
Registrant	Google Inc.
Status	Active Transfer Prohibited by Registry Update Prohibited by Registry Delete Prohibited by Registry Registered until cancelled
WHOIS Server	whois.je
RDAP Nameservers	ns1.google.com ns2.google.com ns3.google.com ns4.google.com

● 🌐 DNS Records

PASS

SOA Records (1)

Name	Value	TTL
google.je	ns1.google.com dns-admin.google.com 965142848 900 900 1800 60	60

NS Records (4)

Name	Value	TTL
google.je	ns2.google.com	345600
google.je	ns3.google.com	345600
google.je	ns1.google.com	345600
google.je	ns4.google.com	345600

A Records (1)

Name	Value	TTL
google.je	142.251.218.228	300

AAAA Records (1)

Name	Value	TTL
google.je	2607:f8b0:4005:815::2004	300

MX Records (1)

Name	Value	TTL
google.je		300

TXT Records (1)

Name	Value	TTL
google.je	v=spf1 -all	300

CAA Records (1)

Name	Value	TTL
google.je	0 issue "pki.goog"	86400

● 🔗 Parent Nameservers

PASS

Nameserver	IPv4	IPv6	Glue
ns3.google.com	216.239.36.10	2001:4860:4802:36::a	No
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
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.je. ns1.google.com ns2.google.com ns3.google.com ns4.google.com
✓	Minimum Nameserver Count	4 nameservers found. Good redundancy.
✓	Public IP: ns3.google.com	Nameserver ns3.google.com has a public IP address.
✓	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: 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	✓	38ms

✓	Authoritative Nameservers Found	Found 4 authoritative nameserver(s): ns3.google.com, ns2.google.com, ns1.google.com, ns4.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.je.
✓	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)

FAIL

Priority	Hostname	IPv4	IPv6	PTR
0		-	-	-

✓	MX Records Exist	Found 1 MX record(s) for google.je.
⚠	MX Redundancy	Only one MX record found. A single mail server is a single point of failure. Consider adding a backup MX.
✗	MX Hostname:	MX record has an invalid hostname:
⚠	MX Reverse DNS (PTR)	No PTR records found for MX server IP(s). Many mail servers require rDNS for spam filtering.
✓	MX Consistency	All authoritative nameservers return consistent MX records.

● 🌍 WWW / Web

INFO

Target	Type	IPs
www.google.je	A	142.251.219.131, 2607:f8b0:4005:818::2003

✓	WWW Record	www.google.je resolves to: 142.251.219.131, 2607:f8b0:4005:818::2003
ℹ	WWW vs Apex IP	www.google.je and google.je 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
je	✓	✓	✓	PASS
google.je	—	—	—	INFO

ℹ

DNSSEC Status

DNSSEC is not enabled for google.je. No DS or DNSKEY records found.

● 🛡️ Email Security

INFO

SPF (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 (1.1.1.1)	US (Cloudflare)	142.250.72.196	23ms
✓	OpenDNS (208.67.222.222)	US (OpenDNS)	142.251.219.4	31ms
✓	Google Public DNS 2 (8.8.4.4)	US (Google)	142.251.219.4	33ms
✓	Google Public DNS (8.8.8.8)	US (Google)	142.251.219.4	35ms
✓	Cloudflare 2 (1.0.0.1)	US (Cloudflare)	142.250.72.196	38ms
✓	Quad9 (9.9.9.9)	US (Quad9)	142.251.34.68	31ms
✓	Comodo Secure (8.26.56.26)	US (Comodo)	142.251.32.164	66ms
✓	OpenDNS 2 (208.67.220.220)	US (OpenDNS)	142.251.219.4	32ms
✓	Verisign (64.6.64.6)	US (Verisign)	142.251.45.4	180ms
✓	Yandex.DNS (77.88.8.8)	RU (Yandex)	172.217.21.196	218ms