leadinglines.com - robtex.com
leadinglines.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.bayshorehosting.com ⚠️ Not in zone NS records | ||||||
| A | 52.203.104.207🇺🇸 Amazon52.200.0.0/13 EC2 IAD prefix | ||||||
| PTR | ec2-52-203-104-207.compute-1.amazonaws.com | ||||||
| NS | ns2.bayshorehosting.com ⚠️ Not in zone NS records | ||||||
| A | 172.214.172.21🇬🇧 Microsoft172.208.0.0/13 | ||||||
| NS | ns3.bayshorehosting.com ⚠️ Not in zone NS records | ||||||
| A | 54.185.219.101🇺🇸 Amazon54.184.0.0/15 EC2 PDX prefix | ||||||
| PTR | ec2-54-185-219-101.us-west-2.compute.amazonaws.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=1778692166 | ||||||
Same first word
leadinglines.com.au |
leadinglines.com |
leadinglines.events |
Similar names
DNS History
6 records (3 active, 3 former)
○NSns0.bayshorehosting.com2015-08-11 → 2017-01-17 · 4 obs
● 2017-01-17 23:55:44
○ 2020-01-05 11:48:50
○ 2026-05-13 17:36:30
●NSns1.bayshorehosting.com2015-08-11 → 2026-05-13 · 2 obs
● 2026-05-13 17:36:30
●NSns2.bayshorehosting.com2015-08-11 → 2026-05-13 · 2 obs
● 2026-05-13 17:36:30
●NSns3.bayshorehosting.com2015-08-11 → 2026-05-13 · 2 obs
● 2026-05-13 17:36:30
○MXmail.leadinglines.com2015-08-11 → 2020-01-05 · 4 obs
● 2020-01-05 11:48:50
○ 2026-04-01 00:33:18
○ 2026-05-13 17:36:30
○A66.77.86.1742015-08-11 → 2020-01-05 · 4 obs
● 2020-01-05 11:48:50
○ 2026-04-01 00:33:18
○ 2026-05-13 17:36:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, e.gtld-servers.net, d.gtld-servers.net, b.gtld-servers.net... | - |
| leadinglines.com | ns1.bayshorehosting.com, ns2.bayshorehosting.com, ns3.bayshorehosting.com | 3 records |
✅ Authoritative Response
Server:52.203.104.207
NS records: ns1.bayshorehosting.com, ns2.bayshorehosting.com, ns3.bayshorehosting.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for leadinglines.com (unsigned zone)
⏱️ Timing
Total: 204ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 3
Out-of-bailiwick: 3 (ns1.bayshorehosting.com, ns2.bayshorehosting.com, ns3.bayshorehosting.com)
Analysis
Name Servers
leadinglines.com is delegated to three name servers: ns1.bayshorehosting.com, ns2.bayshorehosting.com and ns3.bayshorehosting.com.
leadinglines.com at least partially shares name servers with other domains, for instance ny-cruiseshipalliance.com, 115.86.77.66.in-addr.arpa, 41.207.77.66.in-addr.arpa, delegatedagents.net and 197.207.77.66.in-addr.arpa.
Host names with one IP number:
ns1.bayshorehosting.com points to 52.203.104.207.
ns2.bayshorehosting.com points to 172.214.172.21.
ns3.bayshorehosting.com points to 54.185.219.101.