inperm.com - dns.ninja
inperm.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=1782661525 | ||||||
Same first word
inperm.com |
Similar names
DNS History
10 records (4 active, 6 former)
●NSns-cloud-b1.googledomains.com2026-05-01 → 2026-06-28 · 3 obs
● 2026-05-01 13:04:44
● 2026-06-28 15:58:44
●NSns-cloud-b2.googledomains.com2026-05-01 → 2026-06-28 · 3 obs
● 2026-05-01 13:04:44
● 2026-06-28 15:58:44
●NSns-cloud-b3.googledomains.com2026-05-01 → 2026-06-28 · 3 obs
● 2026-05-01 13:04:44
● 2026-06-28 15:58:44
●NSns-cloud-b4.googledomains.com2026-05-01 → 2026-06-28 · 3 obs
● 2026-05-01 13:04:44
● 2026-06-28 15:58:44
○NSns-cloud-d1.googledomains.com2019-12-16 → 2019-12-16 · 3 obs
○ 2026-05-01 13:04:44
○ 2026-06-28 15:58:44
○NSns-cloud-d2.googledomains.com2019-12-16 → 2019-12-16 · 3 obs
○ 2026-05-01 13:04:44
○ 2026-06-28 15:58:44
○NSns-cloud-d3.googledomains.com2019-12-16 → 2019-12-16 · 3 obs
○ 2026-05-01 13:04:44
○ 2026-06-28 15:58:44
○NSns-cloud-d4.googledomains.com2019-12-16 → 2019-12-16 · 3 obs
○ 2026-05-01 13:04:44
○ 2026-06-28 15:58:44
○MXmx.inperm.com.cust.b.hostedemail.com2019-12-16 → 2019-12-16 · 3 obs
○ 2026-05-01 13:04:44
○ 2026-06-28 15:58:44
○A23.227.38.652019-12-16 → 2019-12-16 · 3 obs
○ 2026-05-01 13:04:44
○ 2026-06-28 15:58:44
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | h.gtld-servers.net, k.gtld-servers.net, f.gtld-servers.net, i.gtld-servers.net... | - |
| inperm.com | ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com | 8 records |
✅ Authoritative Response
Server:216.239.38.107
NS records: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 335ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns-cloud-b2.googledomains.com, ns-cloud-b1.googledomains.com... |
| SOA | 1 | ns-cloud-b1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns-cloud-b1.googledomains.com, ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com...)
Analysis
Name Servers
inperm.com has four authoritative name servers: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com and ns-cloud-b4.googledomains.com.
inperm.com has at least partial name server overlap with other domains, such as asjewelrydesign.com, jsk-services.com, trylista.com and two others.
ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com and ns-cloud-b4.googledomains.com all point to exactly two IP numbers each: ns-cloud-b1.googledomains.com → 216.239.32.107 and 2001:4860:4802:32::6b; ns-cloud-b2.googledomains.com → 216.239.34.107 and 2001:4860:4802:34::6b; ns-cloud-b3.googledomains.com → 216.239.36.107 and 2001:4860:4802:36::6b; ns-cloud-b4.googledomains.com → 216.239.38.107 and 2001:4860:4802:38::6b.