finallywed.com - dns.ninja
finallywed.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 3.33.152.147🇺🇸 Amazon3.33.144.0/20 | ||||||
| PTR | a4ec4c6ea1c92e2e6.awsglobalaccelerator.com | ||||||
| A | 15.197.142.173🇺🇸 Amazon15.197.128.0/20 | ||||||
| NS | ns11.domaincontrol.com ⭐ | ||||||
| A | 2603:5:2190::6🇺🇸 GODADDY-DNS2603:5:2190::/44 | ||||||
| PTR | ns11.domaincontrol.com | ||||||
| A | 97.74.105.6🇺🇸 GODADDY-DNS97.74.104.0/23 | ||||||
| PTR | ns11.domaincontrol.com | ||||||
| NS | ns12.domaincontrol.com | ||||||
| A | 2603:5:2290::6🇺🇸 GODADDY-DNS2603:5:2290::/44 | ||||||
| PTR | ns12.domaincontrol.com | ||||||
| A | 173.201.73.6🇺🇸 GODADDY-DNS173.201.72.0/23 | ||||||
| PTR | ns12.domaincontrol.com | ||||||
| TXT | google-site-verification=6k80IP_0X6BhX-OCeALSI9QJ13U-osQwytlAMNqh5a0 | ||||||
| SOA | ns11.domaincontrol.comdns@jomax.net 2021-10-15 #0 | ||||||
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=1786710114 | ||||||
Same first word
finallywed.com |
DNS History
4 records (4 active, 0 former)
●NSns11.domaincontrol.com2026-03-28 → 2026-08-14 · 2 obs
● 2026-08-14 12:27:58
●NSns12.domaincontrol.com2026-03-28 → 2026-08-14 · 2 obs
● 2026-08-14 12:27:58
●A15.197.142.1732026-03-28 → 2026-08-14 · 2 obs
● 2026-08-14 12:27:58
●A3.33.152.1472026-03-28 → 2026-08-14 · 2 obs
● 2026-08-14 12:27:58
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | e.gtld-servers.net, h.gtld-servers.net, j.gtld-servers.net, b.gtld-servers.net... | - |
| finallywed.com | ns11.domaincontrol.com, ns12.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.73.6
NS records: ns11.domaincontrol.com, ns12.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for finallywed.com (unsigned zone)
⏱️ Timing
Total: 100ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 15.197.142.173, 3.33.152.147 |
| NS | 2 | ns11.domaincontrol.com, ns12.domaincontrol.com |
| TXT | 1 | google-site-verification=6k80IP_0X6BhX-O |
| SOA | 1 | ns11.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns11.domaincontrol.com, ns11.domaincontrol.com, ns12.domaincontrol.com...)
Analysis
IP Addresses
finallywed.com has two IP addresses: 3.33.152.147 and 15.197.142.173
myphotostream.co.uk, bergensnowplowinsurance.com, guardiansoulmates.eu and two other host names share IP numbers with finallywed.com.
Name Servers
Two name servers handle the delegation for finallywed.com: ns11.domaincontrol.com and ns12.domaincontrol.com.
finallywed.com uses the same name servers as several other domains — among them easyfutbol.com, hangareventsarizona.com, ontarioblockchainweek.com and two more.
ns11.domaincontrol.com and ns12.domaincontrol.com both carry two IP addresses. The A records for ns11.domaincontrol.com are 97.74.105.6 and 2603:5:2190::6; the A records for ns12.domaincontrol.com are 173.201.73.6 and 2603:5:2290::6.