miraflow.ai - robtex.com
miraflow.ai
ai
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | v0n0.nic.ai ⭐ | ||||||
| NS | v0n1.nic.ai | ||||||
| NS | v0n2.nic.ai | ||||||
| NS | v0n3.nic.ai | ||||||
| NS | v2n0.nic.ai | ||||||
| NS | v2n1.nic.ai | ||||||
| SOA | v0n0.nic.aihostmaster@donuts.email serial=1784630070 | ||||||
Same first word
Similar names
DNS History
4 records (4 active, 0 former)
●NSpdns1.registrar-servers.com2026-05-04 → 2026-07-21 · 2 obs
● 2026-07-21 10:44:56
●NSpdns2.registrar-servers.com2026-05-04 → 2026-07-21 · 2 obs
● 2026-07-21 10:44:56
●MXsmtp.google.com2026-05-04 → 2026-07-21 · 2 obs
● 2026-07-21 10:44:56
●CNAMEdp8cdpy4znku9.cloudfront.net2026-05-04 → 2026-07-21 · 2 obs
● 2026-07-21 10:44:56
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| ai | v0n0.nic.ai, v0n2.nic.ai, v2n1.nic.ai, v2n0.nic.ai... | - |
| miraflow.ai | pdns1.registrar-servers.com, pdns2.registrar-servers.com | - |
✅ Authoritative Response
Server:156.154.133.100
NS records: pdns1.registrar-servers.com, pdns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for miraflow.ai (unsigned zone)
⏱️ Timing
Total: 263ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | pdns1.registrar-servers.com, pdns2.registrar-servers.com |
| MX | 1 | smtp.google.com (pri: 1) |
| TXT | 3 | v=spf1 include:_spf.google.com ~all, google-site-verification=X9CfK2cYJhlqS5i... |
| CNAME | 1 | dp8cdpy4znku9.cloudfront.net |
| SOA | 1 | pdns1.registrar-servers.com hostmaster.r |
Analysis
IP Addresses
miraflow.ai directs to 12 IP numbers: 3.166.192.12, 3.166.192.56, 3.166.192.84 and 9 other.
Other host names, for instance mycleanchoiceenergy.com, rakuno.org, rosterelf.com and two other share IP numbers with miraflow.ai.
Name Servers
The NS records for miraflow.ai point to four name servers: ns-482.awsdns-60.com, ns-652.awsdns-17.net, ns-1177.awsdns-19.org and ns-1756.awsdns-27.co.uk.
miraflow.ai has at least partial name server overlap with other domains, such as d3d6ujpbhbu3n4.cloudfront.net, staging-titlecapture.com, health2service.com and two others.
ns-482.awsdns-60.com, ns-652.awsdns-17.net, ns-1177.awsdns-19.org and ns-1756.awsdns-27.co.uk all point to exactly two IP numbers each: ns-482.awsdns-60.com → 205.251.193.226 and 2600:9000:5301:e200::1; ns-652.awsdns-17.net → 205.251.194.140 and 2600:9000:5302:8c00::1; ns-1177.awsdns-19.org → 205.251.196.153 and 2600:9000:5304:9900::1; ns-1756.awsdns-27.co.uk → 205.251.198.220 and 2600:9000:5306:dc00::1.