finally.com - dns.ninja
finally.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=1786077424 | ||||||
rank #263196 in the tld
Subdomains
Same first word
finally.com |
finally.me |
finally.net |
finally.sg |
finally.ru |
finally.mobi |
finally.in |
finally.cn |
finally.chat |
finally.ie |
finally.nl |
finally.coffee |
finally.agency |
finally.se |
finally.run |
finally.forum |
Similar names
DNS History
18 records (11 active, 7 former)
●NSns-110.awsdns-13.com2026-02-15 → 2026-08-07 · 3 obs
● 2026-02-15 18:20:00
● 2026-08-07 04:46:34
●NSns-1437.awsdns-51.org2026-02-15 → 2026-08-07 · 3 obs
● 2026-02-15 18:20:00
● 2026-08-07 04:46:34
●NSns-1587.awsdns-06.co.uk2026-02-15 → 2026-08-07 · 3 obs
● 2026-02-15 18:20:00
● 2026-08-07 04:46:34
●NSns-595.awsdns-10.net2026-02-15 → 2026-08-07 · 3 obs
● 2026-02-15 18:20:00
● 2026-08-07 04:46:34
○NSns1.brandbucket.com2018-12-18 → 2018-12-18 · 4 obs
● 2018-12-18 04:03:18
○ 2026-02-15 18:20:00
○ 2026-08-07 04:46:34
○NSns1.sedoparking.com2007-10-23 → 2007-10-23 · 3 obs
○ 2015-08-10 02:14:04
○ 2026-08-07 04:46:34
○NSns2.brandbucket.com2018-12-18 → 2018-12-18 · 4 obs
● 2018-12-18 04:03:18
○ 2026-02-15 18:20:00
○ 2026-08-07 04:46:34
○NSns2.sedoparking.com2007-10-23 → 2007-10-23 · 3 obs
○ 2015-08-10 02:14:04
○ 2026-08-07 04:46:34
●MXalt1.aspmx.l.google.com2026-02-15 → 2026-08-07 · 2 obs
● 2026-08-07 04:46:34
●MXalt2.aspmx.l.google.com2026-02-15 → 2026-08-07 · 2 obs
● 2026-08-07 04:46:34
●MXalt3.aspmx.l.google.com2026-02-15 → 2026-08-07 · 2 obs
● 2026-08-07 04:46:34
●MXalt4.aspmx.l.google.com2026-02-15 → 2026-08-07 · 2 obs
● 2026-08-07 04:46:34
●MXaspmx.l.google.com2026-02-15 → 2026-08-07 · 2 obs
● 2026-08-07 04:46:34
●A141.193.213.102026-02-15 → 2026-08-07 · 3 obs
● 2026-02-15 18:20:00
● 2026-08-07 04:46:34
●A141.193.213.112026-02-15 → 2026-08-07 · 3 obs
● 2026-02-15 18:20:00
● 2026-08-07 04:46:34
○A2600:1f1c:800:8b00:f57b:5e93:f0f1:8b2f2018-12-18 → 2018-12-18 · 4 obs
● 2018-12-18 04:03:18
○ 2026-02-15 18:20:00
○ 2026-08-07 04:46:34
○A54.183.99.632015-08-10 → 2018-12-18 · 5 obs
● 2015-08-10 02:14:04
● 2018-12-18 04:03:18
○ 2026-02-15 18:20:00
○ 2026-08-07 04:46:34
○A82.98.86.1612007-10-23 → 2007-10-23 · 3 obs
○ 2015-08-10 02:14:04
○ 2026-08-07 04:46:34
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, e.gtld-servers.net, k.gtld-servers.net, b.gtld-servers.net... | - |
| finally.com | ns-110.awsdns-13.com, ns-595.awsdns-10.net, ns-1587.awsdns-06.co.uk, ns-1437.awsdns-51.org | 2 records |
✅ Authoritative Response
Server:205.251.198.51
NS records: ns-110.awsdns-13.com, ns-595.awsdns-10.net, ns-1587.awsdns-06.co.uk, ns-1437.awsdns-51.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for finally.com (unsigned zone)
⏱️ Timing
Total: 391ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 141.193.213.11, 141.193.213.10 |
| NS | 4 | ns-110.awsdns-13.com, ns-1437.awsdns-51.org... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 12 | 1password-site-verification=6DO4QLEMVRAN, MS=40E2F866C5DB433221B1C57AB1760DCB70629... |
| SOA | 1 | ns-1587.awsdns-06.co.uk awsdns-hostmaste |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-110.awsdns-13.com, ns-110.awsdns-13.com)
Analysis
Hierarchy
cards.finally.com and apply.finally.com are both subdomains of finally.com.
IP Addresses
finally.com has two IP addresses: 141.193.213.10 and 141.193.213.11
physician-nurselicensing.com, kred.no, athletify.ca and two other host names share IP numbers with finally.com.
Name Servers
The authoritative name servers for finally.com are ns-110.awsdns-13.com, ns-595.awsdns-10.net, ns-1437.awsdns-51.org and ns-1587.awsdns-06.co.uk.
The name servers of finally.com overlap at least partially with those of other domains — among them takeki.net, autodiscoverredirection3.redehost.com.br, okfurniture.co.za and two more.
Each of the four hosts ns-110.awsdns-13.com, ns-595.awsdns-10.net, ns-1437.awsdns-51.org and ns-1587.awsdns-06.co.uk has two IP addresses. ns-110.awsdns-13.com points to 205.251.192.110 and 2600:9000:5300:6e00::1. ns-595.awsdns-10.net points to 205.251.194.83 and 2600:9000:5302:5300::1. ns-1437.awsdns-51.org points to 205.251.197.157 and 2600:9000:5305:9d00::1. ns-1587.awsdns-06.co.uk points to 205.251.198.51 and 2600:9000:5306:3300::1.
Mail Servers
Five mail servers handle finally.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
finally.com has at least partial mail server overlap with other domains such as simplygoodwork.com, thci.us, paulyoder.wpengine.com and two more.
These mail servers commonly co-occur with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Hostnames that resolve to two IP addresses:
aspmx.l.google.com maps to two IP addresses — 142.251.167.26 and 2607:f8b0:4004:c0b::1b.
alt1.aspmx.l.google.com maps to two IP addresses — 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com maps to two IP addresses — 172.253.116.27 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com maps to two IP addresses — 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com maps to two IP addresses — 172.253.157.27 and 2a00:1450:400c:c23::1a.