droidtimeclock.com - dns.ninja
droidtimeclock.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=1783197346 | ||||||
Same first word
droidtimeclock.com |
DNS History
10 records (8 active, 2 former)
●NSdns1.registrar-servers.com2026-03-25 → 2026-07-04 · 3 obs
● 2026-03-25 01:28:54
● 2026-07-04 21:02:14
●NSdns2.registrar-servers.com2026-03-25 → 2026-07-04 · 3 obs
● 2026-03-25 01:28:54
● 2026-07-04 21:02:14
○NSpdns05.domaincontrol.com2016-12-17 → 2017-11-17 · 4 obs
● 2017-11-17 17:33:44
○ 2026-03-25 01:28:54
○ 2026-07-04 21:02:14
○NSpdns06.domaincontrol.com2016-12-17 → 2017-11-17 · 4 obs
● 2017-11-17 17:33:44
○ 2026-03-25 01:28:54
○ 2026-07-04 21:02:14
●MXalt1.aspmx.l.google.com2016-12-17 → 2026-07-04 · 2 obs
● 2026-07-04 21:02:14
●MXalt2.aspmx.l.google.com2016-12-17 → 2026-07-04 · 2 obs
● 2026-07-04 21:02:14
●MXaspmx.l.google.com2016-12-17 → 2026-07-04 · 2 obs
● 2026-07-04 21:02:14
●MXaspmx2.googlemail.com2016-12-17 → 2026-07-04 · 2 obs
● 2026-07-04 21:02:14
●MXaspmx3.googlemail.com2016-12-17 → 2026-07-04 · 2 obs
● 2026-07-04 21:02:14
●A96.58.248.1392016-12-17 → 2026-07-04 · 2 obs
● 2026-07-04 21:02:14
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | f.gtld-servers.net, b.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net... | - |
| droidtimeclock.com | dns1.registrar-servers.com, dns2.registrar-servers.com | 4 records |
✅ Authoritative Response
Server:156.154.132.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for droidtimeclock.com (unsigned zone)
⏱️ Timing
Total: 279ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 96.58.248.139 |
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | google-site-verification=yJCIbabigGA2li6 |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)
Analysis
IP Addresses
droidtimeclock.com resolves to just one IP address, 96.58.248.139.
syn-096-058-248-139.biz.spectrum.com is an example of another host name that shares IP numbers with droidtimeclock.com.
Name Servers
droidtimeclock.com has two authoritative name servers — dns1.registrar-servers.com and dns2.registrar-servers.com.
droidtimeclock.com shares its NS records with other domains, for example cfscnextstepk.today, securesoa.com, idear3d.com and two others.
At least some of droidtimeclock.com's name servers are shared with other domains, for example energyflowdance.com, courageoil.net, bwcplumbing.com and two more.
It is common for these name servers to be used in conjunction with the name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com.
Both dns1.registrar-servers.com and dns2.registrar-servers.com have two IP addresses each. dns1.registrar-servers.com resolves to 156.154.132.200 and 2610:a1:1024::200; dns2.registrar-servers.com resolves to 156.154.133.200 and 2610:a1:1025::200.
Mail Servers
Five mail servers handle droidtimeclock.com: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
There is at least a partial MX overlap between droidtimeclock.com and other domains, including ns500768.ns500698.ns500759.ns500736.ns500698.ns500576.ns500576.ns500576.ns500708.ns500698.ns500652.ns500576.trackreceptor.com, agencyarts.biz, wichurches.org and two others.
These mail servers tend to appear in combination with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com resolves to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com resolves to 64.233.180.27 and 2607:f8b0:4004:c25::1b.
alt1.aspmx.l.google.com resolves to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1b.
The host names aspmx2.googlemail.com and alt1.aspmx.l.google.com both resolve to 2800:3f0:4003:c0f::1a IP addresses.
The host names aspmx2.googlemail.com and alt1.aspmx.l.google.com both resolve to 108.177.123.26 IP addresses.
The host names aspmx3.googlemail.com and alt2.aspmx.l.google.com both resolve to 2a00:1450:400b:c02::1b IP addresses.
The host names aspmx3.googlemail.com and alt2.aspmx.l.google.com both resolve to 172.253.116.27 IP addresses.