letscompliance.com - dns.ninja
letscompliance.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.mydomain.com | ||||||
| A | 172.64.52.99🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns2.mydomain.com | ||||||
| A | 172.64.53.76🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| TXT | v=spf1 ip4:66.96.128.0/18 include:websitewelcome.com ?all | ||||||
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=1785209772 | ||||||
Subdomains
Same first word
letscompliance.com |
DNS History
8 records (2 active, 6 former)
●NSns1.mydomain.com2026-03-23 → 2026-07-28 · 2 obs
● 2026-07-28 04:01:10
●NSns2.mydomain.com2026-03-23 → 2026-07-28 · 2 obs
● 2026-07-28 04:01:10
○MXalt1.aspmx.l.google.com2026-03-23 → 2026-03-23 · 2 obs
○ 2026-07-28 04:01:10
○MXalt2.aspmx.l.google.com2026-03-23 → 2026-03-23 · 2 obs
○ 2026-07-28 04:01:10
○MXalt3.aspmx.l.google.com2026-03-23 → 2026-03-23 · 2 obs
○ 2026-07-28 04:01:10
○MXalt4.aspmx.l.google.com2026-03-23 → 2026-03-23 · 2 obs
○ 2026-07-28 04:01:10
○MXaspmx.l.google.com2026-03-23 → 2026-03-23 · 2 obs
○ 2026-07-28 04:01:10
○A66.96.163.1382026-03-23 → 2026-03-23 · 2 obs
○ 2026-07-28 04:01:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | d.gtld-servers.net, e.gtld-servers.net, k.gtld-servers.net, c.gtld-servers.net... | - |
| letscompliance.com | ns1.mydomain.com, ns2.mydomain.com | 2 records |
✅ Authoritative Response
Server:172.64.53.76
NS records: ns1.mydomain.com, ns2.mydomain.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for letscompliance.com (unsigned zone)
⏱️ Timing
Total: 3154ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 66.96.163.138 |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.mydomain.com, ns2.mydomain.com)
Analysis
Hierarchy
ns1.letscompliance.com and mx.letscompliance.com are both subdomains of letscompliance.com.
Name Servers
The NS records for letscompliance.com delegate to ns1.mydomain.com and ns2.mydomain.com.
letscompliance.com uses the same name servers as several other domains — among them achauthorization.com, tech-labs.pro, atomiclion.net and two more.
There is at least partial name server overlap between letscompliance.com and other domains — mackeith.org, mydocteur.com, 800-hot-hott.com and two more among them.
These name servers tend to appear in combination with the name servers ns3.mydomain.com, ns1.yourhostingaccount.com, ns4.mydomain.com and ns2.yourhostingaccount.com.
ns1.mydomain.com → 172.64.52.99 and ns2.mydomain.com → 172.64.53.76: one IP number per host name.