dployme.com - dns.ninja
dployme.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=1782899796 | ||||||
Subdomains
disneyclone.dployme.com |
Same first word
dployme.com |
Similar names
DNS History
14 records (8 active, 6 former)
○NSns1.hostinger.com.br2016-12-18 → 2016-12-18 · 3 obs
○ 2026-03-29 07:19:56
○ 2026-07-01 10:23:28
○NSns2.hostinger.com.br2016-12-18 → 2016-12-18 · 3 obs
○ 2026-03-29 07:19:56
○ 2026-07-01 10:23:28
●NSns21.domaincontrol.com2026-03-29 → 2026-07-01 · 3 obs
● 2026-03-29 07:19:56
● 2026-07-01 10:23:28
●NSns22.domaincontrol.com2026-03-29 → 2026-07-01 · 3 obs
● 2026-03-29 07:19:56
● 2026-07-01 10:23:28
○NSns3.hostinger.com.br2016-12-18 → 2016-12-18 · 3 obs
○ 2026-03-29 07:19:56
○ 2026-07-01 10:23:28
○NSns4.hostinger.com.br2016-12-18 → 2016-12-18 · 3 obs
○ 2026-03-29 07:19:56
○ 2026-07-01 10:23:28
●MXalt1.aspmx.l.google.com2026-03-29 → 2026-07-01 · 3 obs
● 2026-03-29 07:19:56
● 2026-07-01 10:23:28
●MXalt2.aspmx.l.google.com2026-03-29 → 2026-07-01 · 3 obs
● 2026-03-29 07:19:56
● 2026-07-01 10:23:28
●MXalt3.aspmx.l.google.com2026-03-29 → 2026-07-01 · 3 obs
● 2026-03-29 07:19:56
● 2026-07-01 10:23:28
●MXalt4.aspmx.l.google.com2026-03-29 → 2026-07-01 · 3 obs
● 2026-03-29 07:19:56
● 2026-07-01 10:23:28
●MXaspmx.l.google.com2026-03-29 → 2026-07-01 · 3 obs
● 2026-03-29 07:19:56
● 2026-07-01 10:23:28
○MXmx1.hostinger.com.br2016-12-18 → 2016-12-18 · 3 obs
○ 2026-03-29 07:19:56
○ 2026-07-01 10:23:28
○A185.28.21.1702016-12-18 → 2016-12-18 · 3 obs
○ 2026-03-29 07:19:56
○ 2026-07-01 10:23:28
●A75.2.60.52026-03-29 → 2026-07-01 · 3 obs
● 2026-03-29 07:19:56
● 2026-07-01 10:23:28
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | b.gtld-servers.net, j.gtld-servers.net, i.gtld-servers.net, f.gtld-servers.net... | - |
| dployme.com | ns21.domaincontrol.com, ns22.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.68.11
NS records: ns21.domaincontrol.com, ns22.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for dployme.com (unsigned zone)
⏱️ Timing
Total: 763ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 75.2.60.5 |
| NS | 2 | ns21.domaincontrol.com, ns22.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 3 | google-site-verification=Z0xKEsrt4nSM6fA, google-site-verification=C2vm0xDkTM6btZx... |
| SOA | 1 | ns21.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns21.domaincontrol.com, ns21.domaincontrol.com, ns22.domaincontrol.com...)
Analysis
Hierarchy
dployme.com is the parent zone for disneyclone.dployme.com.
IP Addresses
dployme.com has exactly one IP address — 75.2.60.5.
tgntc.com, slimms.com, innovationdept.com plus two other host names have IP numbers in common with dployme.com.
Name Servers
The NS records for dployme.com delegate to ns21.domaincontrol.com and ns22.domaincontrol.com.
The name server configuration of dployme.com is shared with other domains, for instance jimsappliancesofinman.com, amersuit.com, keneti.com and two others.
ns21.domaincontrol.com resolves to 97.74.100.11 and 2603:5:2141::b. Likewise, ns22.domaincontrol.com resolves to 173.201.68.11 and 2603:5:2241::b — two IP addresses apiece.
Mail Servers
Mail for dployme.com is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
At least some of the mail servers used by dployme.com are shared with other domains: big-boom.com.au, ns500742.ns500671.ns500754.ns500754.ns500754.ns500742.ns500671.ns500688.ns500688.ns500704.ns500688.ns500688.ns500649.ns500649.ns500666.ns500142.lusty(0x736c7574)z.com, ns500758.ns500758.ns500759.ns500758.ns500698.ns500698.ns500736.ns500698.ns500735.ns500736.ns500735.ns500708.ns500619.ns500576.ns500652.trackreceptor.com and two others among them.
These mail servers are often deployed together with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 other mail servers.
Host names pointing to two IP addresses:
The A records for aspmx.l.google.com return 173.194.45.26 and 2607:f8b0:4004:c29::1a.
The A records for alt1.aspmx.l.google.com return 108.177.123.27 and 2800:3f0:4003:c0f::1b.
The A records for alt2.aspmx.l.google.com return 172.253.116.27 and 2a00:1450:400b:c02::1a.
The A records for alt3.aspmx.l.google.com return 192.178.223.27 and 2a00:1450:4009:c0f::1b.
The A records for alt4.aspmx.l.google.com return 172.253.157.26 and 2a00:1450:400c:c23::1a.