blanova.com - dns.ninja
blanova.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=1782910646 | ||||||
Same first word
Similar names
DNS History
12 records (7 active, 5 former)
●NSns1-37.azure-dns.com2026-06-26 → 2026-07-01 · 3 obs
● 2026-06-26 23:39:30
● 2026-07-01 12:59:40
○NSns1.netnames.net2015-07-18 → 2018-06-22 · 4 obs
● 2018-06-22 19:52:26
○ 2026-06-26 23:39:30
○ 2026-07-01 12:59:40
●NSns2-37.azure-dns.net2026-06-26 → 2026-07-01 · 3 obs
● 2026-06-26 23:39:30
● 2026-07-01 12:59:40
○NSns2.netnames.net2015-07-18 → 2018-06-22 · 4 obs
● 2018-06-22 19:52:26
○ 2026-06-26 23:39:30
○ 2026-07-01 12:59:40
●NSns3-37.azure-dns.org2026-06-26 → 2026-07-01 · 3 obs
● 2026-06-26 23:39:30
● 2026-07-01 12:59:40
●NSns4-37.azure-dns.info2026-06-26 → 2026-07-01 · 3 obs
● 2026-06-26 23:39:30
● 2026-07-01 12:59:40
●MXrelay1.netnames.net2015-07-18 → 2026-07-01 · 2 obs
● 2026-07-01 12:59:40
●MXrelay2.netnames.net2015-07-18 → 2026-07-01 · 2 obs
● 2026-07-01 12:59:40
○A150.171.109.1182026-06-26 → 2026-06-26 · 4 obs
● 2026-06-26 23:39:30
○ 2026-06-27 00:18:10
○ 2026-07-01 12:59:40
○A150.171.109.342026-06-27 → 2026-06-27 · 4 obs
● 2026-06-27 00:18:10
○ 2026-07-01 12:59:38
○ 2026-07-01 12:59:40
●A150.171.109.732026-07-01 → 2026-07-01 · 3 obs
● 2026-07-01 12:59:38
● 2026-07-01 12:59:40
○A185.26.230.1292015-07-18 → 2018-06-22 · 4 obs
● 2018-06-22 19:52:26
○ 2026-06-26 23:39:30
○ 2026-07-01 12:59:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| blanova.com | ns1-37.azure-dns.com, ns2-37.azure-dns.net, ns4-37.azure-dns.info, ns3-37.azure-dns.org | 2 records |
✅ Authoritative Response
Server:13.107.206.37
NS records: ns1-37.azure-dns.com, ns2-37.azure-dns.net, ns4-37.azure-dns.info, ns3-37.azure-dns.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for blanova.com (unsigned zone)
⏱️ Timing
Total: 471ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 150.171.109.74 |
| NS | 4 | ns1-37.azure-dns.com, ns2-37.azure-dns.net... |
| MX | 2 | relay1.netnames.net (pri: 10), relay2.netnames.net (pri: 100) |
| TXT | 1 | v=spf1 include:azelis.com -all |
| SOA | 1 | ns1-37.azure-dns.com azuredns-hostmaster |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1-37.azure-dns.com, ns1-37.azure-dns.com)
Analysis
IP Addresses
blanova.com resolves to one IP address: 150.171.109.73.
digitalimik.gl, culversfounders.com, leaculver.com and two other host names share IP numbers with blanova.com.
Name Servers
The authoritative name servers for blanova.com are ns1-37.azure-dns.com, ns4-37.azure-dns.info, ns2-37.azure-dns.net and ns3-37.azure-dns.org.
The name servers of blanova.com overlap at least partially with those of other domains — among them concept2.co.uk, ikwileensuzuki.nl, microsoftshield.us and two more.
Each of the four hosts ns1-37.azure-dns.com, ns4-37.azure-dns.info, ns2-37.azure-dns.net and ns3-37.azure-dns.org has two IP addresses. ns1-37.azure-dns.com points to 150.171.10.37 and 2603:1061:0:10::25. ns4-37.azure-dns.info points to 13.107.206.37 and 2620:1ec:bda:10::25. ns2-37.azure-dns.net points to 150.171.16.37 and 2620:1ec:8ec:10::25. ns3-37.azure-dns.org points to 13.107.222.37 and 2a01:111:4000:10::25.
Mail Servers
Mail for blanova.com is handled by two mail servers — relay1.netnames.net and relay2.netnames.net.
blanova.com uses an identical mail server configuration to several other domains — among them pimco.business, allianzassistance.lt, metsa-tissue.pl and two more.
Both relay1.netnames.net and relay2.netnames.net have a single IP address each — relay1.netnames.net resolves to 185.26.230.83 while relay2.netnames.net resolves to 185.26.230.89.