get.how - dns.ninja
get.how
| DNSSEC | ⚠️ Not signed | ||||||
| A | 2001:4860:4802:32::1b🇺🇸 Google2001:4860::/32 | ||||||
| PTR | any-in-2001-4860-4802-32--1b.1e100.net | ||||||
| A | 216.239.32.27🇺🇸 Google216.239.32.0/24 | ||||||
| NS | ns1.zdns.google ⭐ | ||||||
| A | 2001:4860:4802:32::72🇺🇸 Google2001:4860::/32 | ||||||
| PTR | ns1.zdns.google | ||||||
| A | 216.239.32.114🇺🇸 Google216.239.32.0/24 | ||||||
| PTR | ns1.zdns.google | ||||||
| NS | ns2.zdns.google | ||||||
| A | 2001:4860:4802:34::72🇺🇸 Google2001:4860::/32 | ||||||
| PTR | ns2.zdns.google | ||||||
| A | 216.239.34.114🇺🇸 Google216.239.34.0/24 | ||||||
| PTR | ns2.zdns.google | ||||||
| NS | ns3.zdns.google | ||||||
| A | 2001:4860:4802:36::72🇺🇸 Google2001:4860::/32 | ||||||
| PTR | ns3.zdns.google | ||||||
| A | 216.239.36.114🇺🇸 Google216.239.36.0/24 | ||||||
| PTR | ns3.zdns.google | ||||||
| NS | ns4.zdns.google | ||||||
| A | 2001:4860:4802:38::72🇺🇸 Google2001:4860::/32 | ||||||
| PTR | ns4.zdns.google | ||||||
| A | 216.239.38.114🇺🇸 Google216.239.38.0/24 | ||||||
| PTR | ns4.zdns.google | ||||||
| TXT | google-site-verification=jdrerNtWQIR4W9_vQUiSUH9l_TqZtvANCW5ur2DTHnA | ||||||
| SOA | ns1.zdns.googlecloud-dns-hostmaster@google.com serial=1 | ||||||
how
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns-tld1.charlestonroadregistry.com ⭐ | ||||||
| NS | ns-tld2.charlestonroadregistry.com | ||||||
| NS | ns-tld3.charlestonroadregistry.com | ||||||
| NS | ns-tld4.charlestonroadregistry.com | ||||||
| NS | ns-tld5.charlestonroadregistry.com | ||||||
| SOA | ns-tld1.charlestonroadregistry.comcloud-dns-hostmaster@google.com serial=1 | ||||||
Same first word
Similar names
DNS History
11 records (6 active, 5 former)
○NSns1.googledomains.com2016-12-10 → 2017-11-06 · 4 obs
● 2017-11-06 23:14:10
○ 2026-02-17 06:07:00
○ 2026-07-24 12:01:20
●NSns1.zdns.google2026-02-17 → 2026-07-24 · 3 obs
● 2026-02-17 06:07:00
● 2026-07-24 12:01:20
○NSns2.googledomains.com2016-12-10 → 2017-11-06 · 4 obs
● 2017-11-06 23:14:10
○ 2026-02-17 06:07:00
○ 2026-07-24 12:01:20
●NSns2.zdns.google2026-02-17 → 2026-07-24 · 3 obs
● 2026-02-17 06:07:00
● 2026-07-24 12:01:20
○NSns3.googledomains.com2016-12-10 → 2017-11-06 · 4 obs
● 2017-11-06 23:14:10
○ 2026-02-17 06:07:00
○ 2026-07-24 12:01:20
●NSns3.zdns.google2026-02-17 → 2026-07-24 · 3 obs
● 2026-02-17 06:07:00
● 2026-07-24 12:01:20
○NSns4.googledomains.com2016-12-10 → 2017-11-06 · 4 obs
● 2017-11-06 23:14:10
○ 2026-02-17 06:07:00
○ 2026-07-24 12:01:20
●NSns4.zdns.google2026-02-17 → 2026-07-24 · 3 obs
● 2026-02-17 06:07:00
● 2026-07-24 12:01:20
●A2001:4860:4802:32::1b2026-02-17 → 2026-07-24 · 3 obs
● 2026-02-17 06:07:00
● 2026-07-24 12:01:20
●A216.239.32.272026-02-17 → 2026-07-24 · 3 obs
● 2026-02-17 06:07:00
● 2026-07-24 12:01:20
○A216.239.32.292016-12-10 → 2017-11-06 · 4 obs
● 2017-11-06 23:14:10
○ 2026-02-17 06:07:00
○ 2026-07-24 12:01:20
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| how | ns-tld4.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com... | 10 records |
| get.how | ns3.zdns.google, ns1.zdns.google, ns4.zdns.google, ns2.zdns.google | - |
✅ Authoritative Response
Server:216.239.34.114
NS records: ns3.zdns.google, ns1.zdns.google, ns4.zdns.google, ns2.zdns.google
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for get.how (unsigned zone)
⏱️ Timing
Total: 864ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 216.239.32.27 |
| AAAA | 1 | 2001:4860:4802:32::1b |
| NS | 4 | ns3.zdns.google, ns4.zdns.google... |
| TXT | 1 | google-site-verification=jdrerNtWQIR4W9_ |
| SOA | 1 | ns1.zdns.google cloud-dns-hostmaster.goo |
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld5.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)
Analysis
IP Addresses
get.how has two IP addresses: 216.239.32.27 and 2001:4860:4802:32::1b
Among the host names that share IP numbers with get.how are lr-in-x1b.1e100.net, nbupaymentsvendorcerts.com, yyz08s14-in-f27.1e100.net and two others.
Name Servers
The domain get.how is delegated to these four name servers: ns1.zdns.google, ns2.zdns.google, ns3.zdns.google and ns4.zdns.google.
There is at least partial name server overlap between get.how and other domains — on.here, apps.meet, get.new and two more among them.
These name servers are routinely deployed together with the name servers ns1.googledomains.com.
All four hostnames — ns1.zdns.google, ns2.zdns.google, ns3.zdns.google and ns4.zdns.google — resolve to two IP numbers apiece: ns1.zdns.google to 216.239.32.114 and 2001:4860:4802:32::72; ns2.zdns.google to 216.239.34.114 and 2001:4860:4802:34::72; ns3.zdns.google to 216.239.36.114 and 2001:4860:4802:36::72; ns4.zdns.google to 216.239.38.114 and 2001:4860:4802:38::72.