finallycontrol.com - dns.ninja
finallycontrol.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=1783159611 | ||||||
Same first word
finallycontrol.com |
DNS History
9 records (7 active, 2 former)
●NSmaxim.ns.cloudflare.com2026-03-08 → 2026-07-04 · 2 obs
● 2026-07-04 10:21:06
●NSsurina.ns.cloudflare.com2026-03-08 → 2026-07-04 · 2 obs
● 2026-07-04 10:21:06
●MXfinallycontrol-com.mail.protection.outlook.com2026-03-08 → 2026-07-04 · 2 obs
● 2026-07-04 10:21:06
●A104.21.8.1782026-03-08 → 2026-07-04 · 2 obs
● 2026-07-04 10:21:06
●A172.67.157.2042026-03-08 → 2026-07-04 · 2 obs
● 2026-07-04 10:21:06
○A2606:4700:3031::ac43:9dcc2026-03-08 → 2026-06-01 · 4 obs
● 2026-06-01 14:15:04
○ 2026-07-04 10:21:04
○ 2026-07-04 10:21:06
○A2606:4700:3034::6815:8b22026-03-08 → 2026-06-01 · 4 obs
● 2026-06-01 14:15:04
○ 2026-07-04 10:21:04
○ 2026-07-04 10:21:06
●A2606:4700:3035::ac43:9dcc2026-07-04 → 2026-07-04 · 3 obs
● 2026-07-04 10:21:04
● 2026-07-04 10:21:06
●A2606:4700:3036::6815:8b22026-07-04 → 2026-07-04 · 3 obs
● 2026-07-04 10:21:04
● 2026-07-04 10:21:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| finallycontrol.com | surina.ns.cloudflare.com, maxim.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server:108.162.195.198
NS records: surina.ns.cloudflare.com, maxim.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for finallycontrol.com (unsigned zone)
⏱️ Timing
Total: 190ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 104.21.8.178, 172.67.157.204 |
| AAAA | 2 | 2606:4700:3035::ac43:9dcc, 2606:4700:3036::6815:8b2 |
| NS | 2 | maxim.ns.cloudflare.com, surina.ns.cloudflare.com |
| MX | 1 | finallycontrol-com.mail.protection.outlo |
| TXT | 1 | v=spf1 include:spf.protection.outlook.co |
| HTTPS | 1 | {"priority":1,"target":".","alpn":["h3", |
| SOA | 1 | maxim.ns.cloudflare.com dns.cloudflare.c |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (surina.ns.cloudflare.com, surina.ns.cloudflare.com, surina.ns.cloudflare.com...)
Analysis
IP Addresses
finallycontrol.com points to the four IP addresses 104.21.8.178, 172.67.157.204, 2606:4700:3035::ac43:9dcc and 2606:4700:3036::6815:8b2.
Two other host names, along with sebastian-menzel.com, hlbexh.com and wopie.com, also share IP numbers with finallycontrol.com.
Name Servers
finallycontrol.com has two authoritative name servers — maxim.ns.cloudflare.com and surina.ns.cloudflare.com.
finallycontrol.com shares its NS records with other domains, for example pasito.app, tomov.eu, restoreconstruction.com and two others.
At least some of finallycontrol.com's name servers are shared with other domains, for example labortribune.com, chemtechholding.com, coparfin.com and two more.
These name servers tend to be used in conjunction with the name servers daphne.ns.cloudflare.com.
DNS names with 6 IP addresses:
maxim.ns.cloudflare.com points to 108.162.195.198, 162.159.44.198, 172.64.35.198 and 3 other IP addresses.
surina.ns.cloudflare.com points to 108.162.194.19, 162.159.38.19, 172.64.34.19 and 3 other IP addresses.
Mail Servers
The sole mail server for finallycontrol.com is finallycontrol-com.mail.protection.outlook.com.
With 8 IP addresses total, finallycontrol-com.mail.protection.outlook.com resolves to 52.101.172.0, 52.101.172.1, 52.101.174.0 and 5 others.