sem.how - dns.ninja

sem.how

how

DNSSECπŸ”’ Signed (DS record present)
NSns-tld1.charlestonroadregistry.com ⭐
NSns-tld2.charlestonroadregistry.com
NSns-tld3.charlestonroadregistry.com
NSns-tld4.charlestonroadregistry.com
NSns-tld5.charlestonroadregistry.com
SOAns-tld1.charlestonroadregistry.comcloud-dns-hostmaster@google.com serial=1

Same first word

Similar names

DNS History

8 records (4 active, 4 former)

2017201820192020202120222023202420252026NSns-cloud-e1.googledomains.comns-cloud-e2.googledomains.comns-cloud-e3.googledomains.comns-cloud-e4.googledomains.comns1.sedoparking.comns2.sedoparking.comMXlocalhostA72.52.4.119
●NSns-cloud-e1.googledomains.com2020-12-27 β†’ 2026-07-17 Β· 3 obs
β—‹ 2016-12-10 13:22:44
● 2020-12-27 14:59:40
● 2026-07-17 15:37:22
●NSns-cloud-e2.googledomains.com2020-12-27 β†’ 2026-07-17 Β· 3 obs
β—‹ 2016-12-10 13:22:44
● 2020-12-27 14:59:40
● 2026-07-17 15:37:22
●NSns-cloud-e3.googledomains.com2020-12-27 β†’ 2026-07-17 Β· 3 obs
β—‹ 2016-12-10 13:22:44
● 2020-12-27 14:59:40
● 2026-07-17 15:37:22
●NSns-cloud-e4.googledomains.com2020-12-27 β†’ 2026-07-17 Β· 3 obs
β—‹ 2016-12-10 13:22:44
● 2020-12-27 14:59:40
● 2026-07-17 15:37:22
β—‹NSns1.sedoparking.com2016-12-10 β†’ 2016-12-10 Β· 3 obs
● 2016-12-10 13:22:44
β—‹ 2020-12-27 14:59:40
β—‹ 2026-07-17 15:37:22
β—‹NSns2.sedoparking.com2016-12-10 β†’ 2016-12-10 Β· 3 obs
● 2016-12-10 13:22:44
β—‹ 2020-12-27 14:59:40
β—‹ 2026-07-17 15:37:22
β—‹MXlocalhost2016-12-10 β†’ 2016-12-10 Β· 3 obs
● 2016-12-10 13:22:44
β—‹ 2020-12-27 14:59:40
β—‹ 2026-07-17 15:37:22
β—‹A72.52.4.1192016-12-10 β†’ 2016-12-10 Β· 3 obs
● 2016-12-10 13:22:44
β—‹ 2020-12-27 14:59:40
β—‹ 2026-07-17 15:37:22

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
howns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com...10 records
sem.howns-cloud-e1.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, ns-cloud-e2.googledomains.com-

βœ… Authoritative Response

Server:216.239.38.110

NS records: ns-cloud-e1.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, ns-cloud-e2.googledomains.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for sem.how (unsigned zone)

⏱️ Timing

Total: 611ms | Queries: -

πŸ“„ Records

TypeCountSample Data
NS4ns-cloud-e4.googledomains.com, ns-cloud-e1.googledomains.com...
SOA1ns-cloud-e1.googledomains.com cloud-dns-

πŸ“Œ Glue Records Collected

Total: 10

Out-of-bailiwick: 10 (ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)

Analysis

Name Servers

Four name servers handle the delegation for sem.how: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com.

sem.how shares at least some of its name servers with other domains, including sasainet.com, totvsstage.com, woolworthsspringwood.com and two others.

The host names ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com each resolve to two IP addresses: ns-cloud-e1.googledomains.com resolves to 216.239.32.110 and 2001:4860:4802:32::6e; ns-cloud-e2.googledomains.com resolves to 216.239.34.110 and 2001:4860:4802:34::6e; ns-cloud-e3.googledomains.com resolves to 216.239.36.110 and 2001:4860:4802:36::6e; ns-cloud-e4.googledomains.com resolves to 216.239.38.110 and 2001:4860:4802:38::6e.