titleknow.com - dns.ninja
titleknow.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 34.102.136.180🇺🇸 Google34.100.0.0/14 | ||||||
| PTR | 180.136.102.34.bc.googleusercontent.com | ||||||
| NS | ns1-e1.fnf.com ⭐ | ||||||
| A | 170.88.179.14🇺🇸 AS54478170.88.179.0/24 | ||||||
| PTR | ns1-e1.fnf.com | ||||||
| NS | ns2-e2.fnf.com | ||||||
| A | 170.88.15.14🇺🇸 AS54478170.88.15.0/24 | ||||||
| PTR | ns2-e2.fnf.com | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns1-e1.fnf.complease_set_email@absolutely.nowhere serial=6 | ||||||
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=1782907031 | ||||||
Same first word
titleknow.com |
Similar names
DNS History
9 records (3 active, 6 former)
○NSdns1.namecheaphosting.com2017-08-11 → 2017-08-11 · 3 obs
○ 2026-03-10 05:05:50
○ 2026-07-01 12:02:22
○NSdns2.namecheaphosting.com2017-08-11 → 2017-08-11 · 3 obs
○ 2026-03-10 05:05:50
○ 2026-07-01 12:02:22
●NSns1-e1.fnf.com2026-03-10 → 2026-07-01 · 3 obs
● 2026-03-10 05:05:50
● 2026-07-01 12:02:22
●NSns2-e2.fnf.com2026-03-10 → 2026-07-01 · 3 obs
● 2026-03-10 05:05:50
● 2026-07-01 12:02:22
○MXsmx1.web-hosting.com2017-08-11 → 2017-08-11 · 3 obs
○ 2026-03-10 05:05:50
○ 2026-07-01 12:02:22
○MXsmx2.web-hosting.com2017-08-11 → 2017-08-11 · 3 obs
○ 2026-03-10 05:05:50
○ 2026-07-01 12:02:22
○MXsmx3.web-hosting.com2017-08-11 → 2017-08-11 · 3 obs
○ 2026-03-10 05:05:50
○ 2026-07-01 12:02:22
○A198.54.116.332017-08-11 → 2017-08-11 · 3 obs
○ 2026-03-10 05:05:50
○ 2026-07-01 12:02:22
●A34.102.136.1802026-03-10 → 2026-07-01 · 3 obs
● 2026-03-10 05:05:50
● 2026-07-01 12:02:22
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| titleknow.com | ns1-e1.fnf.com, ns2-e2.fnf.com | 2 records |
✅ Authoritative Response
Server:170.88.179.14
NS records: ns1-e1.fnf.com, ns2-e2.fnf.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for titleknow.com (unsigned zone)
⏱️ Timing
Total: 301ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 34.102.136.180 |
| NS | 2 | ns1-e1.fnf.com, ns2-e2.fnf.com |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns1-e1.fnf.com please_set_email.absolute |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1-e1.fnf.com, ns2-e2.fnf.com)
Analysis
IP Addresses
titleknow.com resolves to one IP address: 34.102.136.180.
stanleykoh.com, cocause.com, inputmonkey.com and two other host names share IP numbers with titleknow.com.
Name Servers
Two name servers handle the delegation for titleknow.com: ns1-e1.fnf.com and ns2-e2.fnf.com.
titleknow.com uses the same name servers as several other domains — among them smartviewonline.net, allegiancetitle.net, cltica.com and two more.
Both ns1-e1.fnf.com and ns2-e2.fnf.com have a single IP address each — ns1-e1.fnf.com resolves to 170.88.179.14 while ns2-e2.fnf.com resolves to 170.88.15.14.