complete.md - dns.ninja
complete.md
md
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns.dns.md ⭐ | ||||||
| NS | nsa.tld.md | ||||||
| NS | nsb.tld.md | ||||||
| NS | nsc.dns.md | ||||||
| NS | nsf.dns.md | ||||||
| NS | nsr.dns.md ⚠️ Not in zone NS records | ||||||
| SOA | ns.dns.mdmaster@dns.md 2026-08-06 #10 | ||||||
Subdomains
Same first word
Similar names
DNS History
11 records (10 active, 1 former)
●NSns-1086.awsdns-07.org2015-07-18 → 2026-08-06 · 2 obs
● 2026-08-06 07:45:38
●NSns-1737.awsdns-25.co.uk2015-07-18 → 2026-08-06 · 2 obs
● 2026-08-06 07:45:38
●NSns-477.awsdns-59.com2015-07-18 → 2026-08-06 · 2 obs
● 2026-08-06 07:45:38
●NSns-786.awsdns-34.net2015-07-18 → 2026-08-06 · 2 obs
● 2026-08-06 07:45:38
●MXalt1.aspmx.l.google.com2015-07-18 → 2026-08-06 · 5 obs
● 2017-05-20 18:41:30
○ 2026-07-31 01:38:08
● 2026-07-31 05:05:30
● 2026-08-06 07:45:38
●MXalt2.aspmx.l.google.com2015-07-18 → 2026-08-06 · 5 obs
● 2017-05-20 18:41:30
○ 2026-07-31 01:38:08
● 2026-07-31 05:05:30
● 2026-08-06 07:45:38
●MXaspmx.l.google.com2015-07-18 → 2026-08-06 · 5 obs
● 2017-05-20 18:41:30
○ 2026-07-31 01:38:08
● 2026-07-31 05:05:30
● 2026-08-06 07:45:38
●MXaspmx2.googlemail.com2015-07-18 → 2026-08-06 · 5 obs
● 2017-05-20 18:41:30
○ 2026-07-31 01:38:08
● 2026-07-31 05:05:30
● 2026-08-06 07:45:38
●MXaspmx3.googlemail.com2015-07-18 → 2026-08-06 · 5 obs
● 2017-05-20 18:41:30
○ 2026-07-31 01:38:08
● 2026-07-31 05:05:30
● 2026-08-06 07:45:38
○A205.144.218.702015-07-18 → 2017-05-20 · 4 obs
● 2017-05-20 18:41:30
○ 2026-02-22 20:32:16
○ 2026-08-06 07:45:38
●A35.208.31.2312026-02-22 → 2026-08-06 · 5 obs
● 2026-02-22 20:32:16
○ 2026-07-31 01:38:08
● 2026-07-31 05:05:30
● 2026-08-06 07:45:38
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| md | nsa.tld.md, nsb.tld.md, nsf.dns.md, nsc.dns.md... | 8 records |
| complete.md | ns-477.awsdns-59.com, ns-786.awsdns-34.net, ns-1086.awsdns-07.org, ns-1737.awsdns-25.co.uk | - |
✅ Authoritative Response
Server:205.251.198.201
NS records: ns-477.awsdns-59.com, ns-786.awsdns-34.net, ns-1086.awsdns-07.org, ns-1737.awsdns-25.co.uk
🔒 DNSSEC Status
❌ Bogus (DNSSEC validation failed)
Validation error at md: Error: DNS query timeout: 89.32.236.165 for DNSKEY md
⏱️ Timing
Total: 5860ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 35.208.31.231 |
| NS | 4 | ns-1086.awsdns-07.org, ns-1737.awsdns-25.co.uk... |
| MX | 5 | aspmx.l.google.com (pri: 1), aspmx2.googlemail.com (pri: 10)... |
| TXT | 3 | anthropic-domain-verification-993e6f=94M, docusign=2a22e840-4de9-4b6f-811d-5612afa... |
| SOA | 1 | ns-477.awsdns-59.com awsdns-hostmaster.a |
📌 Glue Records Collected
Total: 8
In-bailiwick: 8 (nsr.dns.md, nsf.dns.md, nsc.dns.md...)
Analysis
Hierarchy
complete.md serves as the parent of portal.complete.md and api.complete.md.
IP Addresses
complete.md has exactly one IP address — 35.208.31.231.
flexstarinc.com, recb.co, 144.217.197.wcso.com plus two other host names have IP numbers in common with complete.md.
Name Servers
Four name servers handle the delegation for complete.md: ns-477.awsdns-59.com, ns-786.awsdns-34.net, ns-1086.awsdns-07.org and ns-1737.awsdns-25.co.uk.
complete.md shares at least some of its name servers with other domains, including usdakc.com, royalmelbourne.com.au, d2gy0hmj48ipqr.cloudfront.net and two others.
The host names ns-477.awsdns-59.com, ns-786.awsdns-34.net, ns-1086.awsdns-07.org and ns-1737.awsdns-25.co.uk each resolve to two IP addresses: ns-477.awsdns-59.com resolves to 205.251.193.221 and 2600:9000:5301:dd00::1; ns-786.awsdns-34.net resolves to 205.251.195.18 and 2600:9000:5303:1200::1; ns-1086.awsdns-07.org resolves to 205.251.196.62 and 2600:9000:5304:3e00::1; ns-1737.awsdns-25.co.uk resolves to 205.251.198.201 and 2600:9000:5306:c900::1.
Mail Servers
complete.md is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
At least some of the mail servers used by complete.md are shared with other domains: engall.net, mx1.sli-systems.com, ns500737.ns500724.ns500737.ns500599.ns500724.ns500737.ns500697.ns500583.ns500583.ns500697.ns500583.ns500583.ns500583.www.yummyflingsfinder.com and two others among them.
These mail servers are often deployed together with alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx2.googlemail.com points to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com points to 172.253.116.27 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com points to 172.253.122.26 and 2607:f8b0:4004:c21::1a.
alt1.aspmx.l.google.com points to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com points to 172.253.116.27 and 2a00:1450:400b:c02::1a.
aspmx2.googlemail.com and alt1.aspmx.l.google.com are host names that each point to 2800:3f0:4003:c0f::1b IP addresses.
aspmx2.googlemail.com and alt1.aspmx.l.google.com are host names that each point to 108.177.123.27 IP addresses.
aspmx3.googlemail.com and alt2.aspmx.l.google.com are host names that each point to 2a00:1450:400b:c02::1a IP addresses.
aspmx3.googlemail.com and alt2.aspmx.l.google.com are host names that each point to 172.253.116.27 IP addresses.