android.how - robtex.com
android.how
| DNSSEC | β οΈ Not signed | ||||||
| NS | ns1.google.com β | ||||||
| A | 2001:4860:4802:32::aπΊπΈ Google2001:4860::/32 | ||||||
| PTR | ns1.google.com | ||||||
| A | 216.239.32.10πΊπΈ Google216.239.32.0/24 | ||||||
| PTR | ns1.google.com | ||||||
| NS | ns2.google.com | ||||||
| A | 2001:4860:4802:34::aπΊπΈ Google2001:4860::/32 | ||||||
| PTR | ns2.google.com | ||||||
| A | 216.239.34.10πΊπΈ Google216.239.34.0/24 | ||||||
| PTR | ns2.google.com | ||||||
| NS | ns3.google.com | ||||||
| A | 2001:4860:4802:36::aπΊπΈ Google2001:4860::/32 | ||||||
| PTR | ns3.google.com | ||||||
| A | 216.239.36.10πΊπΈ Google216.239.36.0/24 | ||||||
| PTR | ns3.google.com | ||||||
| NS | ns4.google.com | ||||||
| A | 2001:4860:4802:38::aπΊπΈ Google2001:4860::/32 | ||||||
| PTR | ns4.google.com | ||||||
| A | 216.239.38.10πΊπΈ Google216.239.38.0/24 | ||||||
| PTR | ns4.google.com | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns1.google.comdns-admin@google.com serial=942063489 | ||||||
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
4 records (4 active, 0 former)
βNSns1.google.com2016-12-10 β 2026-07-04 Β· 2 obs
β 2026-07-04 07:08:10
βNSns2.google.com2016-12-10 β 2026-07-04 Β· 2 obs
β 2026-07-04 07:08:10
βNSns3.google.com2016-12-10 β 2026-07-04 Β· 2 obs
β 2026-07-04 07:08:10
βNSns4.google.com2016-12-10 β 2026-07-04 Β· 4 obs
β 2017-08-08 19:38:10
β 2017-08-08 20:13:54
β 2026-07-04 07:08:10
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| how | ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com... | 10 records |
| android.how | ns1.google.com, ns3.google.com, ns4.google.com, ns2.google.com | - |
β Authoritative Response
Server:216.239.38.10
NS records: ns1.google.com, ns3.google.com, ns4.google.com, ns2.google.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for android.how (unsigned zone)
β±οΈ Timing
Total: 192ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1.google.com, ns3.google.com... |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns1.google.com dns-admin.google.com |
π Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld5.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)
Analysis
Name Servers
android.how has four authoritative name servers: ns1.google.com, ns2.google.com, ns3.google.com and ns4.google.com.
android.how partially shares its NS delegation with several other domains, including froogle.us, google-notebook.com, alt4.google.hu and two others.
ns1.google.com, ns2.google.com, ns3.google.com and ns4.google.com each carry two IP addresses. ns1.google.com has 216.239.32.10 and 2001:4860:4802:32::a; ns2.google.com has 216.239.34.10 and 2001:4860:4802:34::a; ns3.google.com has 216.239.36.10 and 2001:4860:4802:36::a; ns4.google.com has 216.239.38.10 and 2001:4860:4802:38::a.