labsignals.com - robtex.com
labsignals.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 52.20.84.62🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix | ||||||
| PTR | ec2-52-20-84-62.compute-1.amazonaws.com | ||||||
| NS | ns1.atom.com ⭐ | ||||||
| A | 44.219.81.145🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix | ||||||
| PTR | ec2-44-219-81-145.compute-1.amazonaws.com | ||||||
| NS | ns2.atom.com | ||||||
| A | 50.19.240.86🇺🇸 Amazon50.19.128.0/17 EC2 IAD prefix | ||||||
| PTR | ec2-50-19-240-86.compute-1.amazonaws.com | ||||||
| TXT | f0095018235b8109a2bf9f65674a1784b6971ed6 | ||||||
| SOA | ns1.atom.comhostmaster@labsignals.com 2025-02-11 #1 | ||||||
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=1785025902 | ||||||
Same first word
labsignals.com |
Similar names
DNS History
6 records (3 active, 3 former)
●NSns1.atom.com2026-06-29 → 2026-07-26 · 3 obs
● 2026-06-29 21:07:58
● 2026-07-26 00:46:00
○NSns1.brandroot.com2016-12-20 → 2017-11-08 · 4 obs
● 2017-11-08 14:16:36
○ 2026-06-29 21:07:58
○ 2026-07-26 00:46:00
●NSns2.atom.com2026-06-29 → 2026-07-26 · 3 obs
● 2026-06-29 21:07:58
● 2026-07-26 00:46:00
○NSns2.brandroot.com2016-12-20 → 2017-11-08 · 4 obs
● 2017-11-08 14:16:36
○ 2026-06-29 21:07:58
○ 2026-07-26 00:46:00
○A45.40.162.1122016-12-20 → 2017-11-08 · 4 obs
● 2017-11-08 14:16:36
○ 2026-06-29 21:07:58
○ 2026-07-26 00:46:00
●A52.20.84.622026-06-29 → 2026-07-26 · 3 obs
● 2026-06-29 21:07:58
● 2026-07-26 00:46:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | d.gtld-servers.net, l.gtld-servers.net, f.gtld-servers.net, i.gtld-servers.net... | - |
| labsignals.com | ns1.atom.com, ns2.atom.com | 2 records |
✅ Authoritative Response
Server:44.219.81.145
NS records: ns1.atom.com, ns2.atom.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for labsignals.com (unsigned zone)
⏱️ Timing
Total: 3163ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.20.84.62 |
| NS | 2 | ns2.atom.com, ns1.atom.com |
| TXT | 1 | f0095018235b8109a2bf9f65674a1784b6971ed6 |
| SOA | 1 | ns1.atom.com hostmaster.labsignals.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)
Analysis
IP Addresses
labsignals.com directs to one IP number, which is 52.20.84.62.
Among the host names that share IP numbers with labsignals.com are darkpro.com, oconos.com, dreamcoda.com and two others.
Name Servers
labsignals.com is delegated to two name servers: ns1.atom.com and ns2.atom.com.
labsignals.com has the same name server delegation as a number of other domains, such as switchpilot.com, rustroom.com, fusionplayer.com and two more.
There is an overlap in name servers between labsignals.com and other domains, for example clubzi.com, afli.com and alkhubar.net
Both ns1.atom.com and ns2.atom.com have a single IP address each — ns1.atom.com resolves to 44.219.81.145 while ns2.atom.com resolves to 50.19.240.86.