royallocks.com - robtex.com
royallocks.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=1771291435 | ||||||
Subdomains
mail.royallocks.com |
Same first word
royallocks.com |
DNS History
14 records (8 active, 6 former)
●NSdns101.register.com2026-02-28 → 2026-03-22 · 3 obs
● 2026-02-28 14:24:10
● 2026-03-22 17:47:32
●NSdns102.register.com2026-02-28 → 2026-03-22 · 3 obs
● 2026-02-28 14:24:10
● 2026-03-22 17:47:32
○NSdns107.b.register.com2015-07-13 → 2018-05-20 · 4 obs
● 2018-05-20 23:22:36
○ 2026-02-28 14:24:10
○ 2026-03-22 17:47:32
○NSdns192.a.register.com2015-07-13 → 2018-05-20 · 4 obs
● 2018-05-20 23:22:36
○ 2026-02-28 14:24:10
○ 2026-03-22 17:47:32
○NSdns209.c.register.com2015-07-13 → 2018-05-20 · 4 obs
● 2018-05-20 23:22:36
○ 2026-02-28 14:24:10
○ 2026-03-22 17:47:32
○NSdns249.d.register.com2015-07-13 → 2018-05-20 · 4 obs
● 2018-05-20 23:22:36
○ 2026-02-28 14:24:10
○ 2026-03-22 17:47:32
●MXalt1.aspmx.l.google.com2026-02-28 → 2026-03-22 · 3 obs
● 2026-02-28 14:24:10
● 2026-03-22 17:47:32
●MXalt2.aspmx.l.google.com2026-02-28 → 2026-03-22 · 3 obs
● 2026-02-28 14:24:10
● 2026-03-22 17:47:32
●MXalt3.aspmx.l.google.com2026-02-28 → 2026-03-22 · 3 obs
● 2026-02-28 14:24:10
● 2026-03-22 17:47:32
●MXalt4.aspmx.l.google.com2026-02-28 → 2026-03-22 · 3 obs
● 2026-02-28 14:24:10
● 2026-03-22 17:47:32
●MXaspmx.l.google.com2026-02-28 → 2026-03-22 · 3 obs
● 2026-02-28 14:24:10
● 2026-03-22 17:47:32
○MXp.webcom.ctmail.com2016-05-06 → 2018-05-20 · 4 obs
● 2018-05-20 23:22:36
○ 2026-02-28 14:24:10
○ 2026-03-22 17:47:32
○A216.21.239.1972015-07-13 → 2018-05-20 · 4 obs
● 2018-05-20 23:22:36
○ 2026-02-28 14:24:10
○ 2026-03-22 17:47:32
●A23.227.38.652026-02-28 → 2026-03-22 · 3 obs
● 2026-02-28 14:24:10
● 2026-03-22 17:47:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| royallocks.com | dns101.register.com, dns102.register.com | 2 records |
✅ Authoritative Response
Server: 162.159.24.117
NS records: dns101.register.com, dns102.register.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for royallocks.com (unsigned zone)
⏱️ Timing
Total: 1097ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 23.227.38.65 |
| NS | 2 | dns102.register.com, dns101.register.com |
| MX | 5 | alt4.aspmx.l.google.com (pri: 10), alt2.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | google-site-verification=QM9QS0Whpr_gZn9, v=spf1 include:_spf.google.com ~all |
| SOA | 1 | DNS101.REGISTER.com root@register.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (dns101.register.com, dns102.register.com)
Analysis
Hierarchy
royallocks.com is a parent of mail.royallocks.com.
IP Addresses
royallocks.com points to a single IP address: 23.227.38.65.
Other host names such as weruva.com, weingut-ernst.de, spielzeugservice24.de, chairbedsuk.co.uk and naturom.ro share IP numbers with royallocks.com.
Name Servers
royallocks.com is delegated to two name servers: dns101.register.com and dns102.register.com.
royallocks.com uses the same name server setup as other domains, including mobilebillboards.info, cartercalvert.com, enugenesis.com, 30daystothin.com and pettway.net.
royallocks.com shares some name servers with other domains, for example sukram.com.
Hostnames with a single IP
dns101.register.com resolves to: 162.159.24.117.
dns102.register.com resolves to: 162.159.25.158.
Mail Servers
royallocks.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.
royallocks.com shares at least some mail servers with other domains, for example ns500731.ns500731.ns500742.ns500742.ns500731.ns500671.ns500688.ns500704.ns500678.ns500678.ns500649.ns500666.ns500653.ns500153.tenderladiesbz.com, ns500671.ns500671.ns500731.ns500742.ns500671.ns500731.ns500671.ns500704.ns500671.ns500649.ns500291.ns500142.lusty(0x736c7574)z.com, ns500698.ns500759.ns500759.ns500735.ns500735.ns500698.ns500698.ns500698.ns500698.ns500619.ns500619.trackreceptor.com, ns500754.ns500731.ns500742.ns500754.ns500671.ns500731.ns500688.ns500688.ns500671.ns500678.ns500671.ns500131.lustychickser.com and berrydivineacai.com.
these mail servers are often used together with aspmx2.googlemail.com and aspmx3.googlemail.com.
Host names with two IP numbers: aspmx.l.google.com points to 2607:f8b0:4004:c19::1b and 172.253.62.27; alt1.aspmx.l.google.com points to 2607:f8b0:4003:c30::1b and 74.125.27.26; alt2.aspmx.l.google.com points to 2607:f8b0:4001:c70::1a and 192.178.209.26; alt3.aspmx.l.google.com points to 2607:f8b0:4024:c0d::1b and 192.178.152.26; alt4.aspmx.l.google.com points to 2607:f8b0:4023:403::1a and 142.250.96.27.