into.com - dns.ninja
into.com
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1785920069 | ||||||
Same first word
Similar names
DNS History
10 records (4 active, 6 former)
●NSns-cloud-a1.googledomains.com2026-03-05 → 2026-08-05 · 3 obs
● 2026-03-05 10:52:18
● 2026-08-05 08:59:04
●NSns-cloud-a2.googledomains.com2026-03-05 → 2026-08-05 · 3 obs
● 2026-03-05 10:52:18
● 2026-08-05 08:59:04
●NSns-cloud-a3.googledomains.com2026-03-05 → 2026-08-05 · 3 obs
● 2026-03-05 10:52:18
● 2026-08-05 08:59:04
●NSns-cloud-a4.googledomains.com2026-03-05 → 2026-08-05 · 3 obs
● 2026-03-05 10:52:18
● 2026-08-05 08:59:04
○NSns-cloud1.googledomains.com2015-08-17 → 2017-05-10 · 4 obs
● 2017-05-10 03:24:14
○ 2026-03-05 10:52:18
○ 2026-08-05 08:59:04
○NSns-cloud2.googledomains.com2015-08-17 → 2017-05-10 · 4 obs
● 2017-05-10 03:24:14
○ 2026-03-05 10:52:18
○ 2026-08-05 08:59:04
○NSns-cloud3.googledomains.com2015-08-17 → 2017-05-10 · 4 obs
● 2017-05-10 03:24:14
○ 2026-03-05 10:52:18
○ 2026-08-05 08:59:04
○NSns-cloud4.googledomains.com2015-08-17 → 2017-05-10 · 4 obs
● 2017-05-10 03:24:14
○ 2026-03-05 10:52:18
○ 2026-08-05 08:59:04
○MXmx.prama.com2015-08-17 → 2017-05-10 · 4 obs
● 2017-05-10 03:24:14
○ 2026-03-05 10:52:18
○ 2026-08-05 08:59:04
○A99.148.75.1872015-08-17 → 2017-05-10 · 4 obs
● 2017-05-10 03:24:14
○ 2026-03-05 10:52:18
○ 2026-08-05 08:59:04
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | b.gtld-servers.net, i.gtld-servers.net, h.gtld-servers.net, g.gtld-servers.net... | - |
| into.com | ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com | 8 records |
✅ Authoritative Response
Server:216.239.38.106
NS records: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 649ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns-cloud-a2.googledomains.com, ns-cloud-a4.googledomains.com... |
| SOA | 1 | ns-cloud-a1.googledomains.com dns-admin. |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns-cloud-a1.googledomains.com, ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com...)
Analysis
Name Servers
The domain into.com is delegated to these four name servers: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com.
into.com shares at least some of its name servers with other domains, including dabtrials.com, toolcardstore.com, ginahasababy.com and two others.
The host names ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com each resolve to two IP addresses: ns-cloud-a1.googledomains.com resolves to 216.239.32.106 and 2001:4860:4802:32::6a; ns-cloud-a2.googledomains.com resolves to 216.239.34.106 and 2001:4860:4802:34::6a; ns-cloud-a3.googledomains.com resolves to 216.239.36.106 and 2001:4860:4802:36::6a; ns-cloud-a4.googledomains.com resolves to 216.239.38.106 and 2001:4860:4802:38::6a.