ipfint.com - dns.ninja
ipfint.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=1786370244 | ||||||
Same first word
ipfint.com |
Similar names
pinfit.com |
fitnip.com |
tipfin.com |
fitpin.com |
pitfin.com |
fintip.cz |
finpit.fi |
ipnfit.com |
pitfin.co.uk |
fintip.ru |
tipinf.com |
fintip.com |
finpit.com |
DNS History
9 records (8 active, 1 former)
●NSns1.netnames.net2016-12-15 → 2026-08-10 · 2 obs
● 2026-08-10 14:17:58
●NSns2.netnames.net2016-12-15 → 2026-08-10 · 2 obs
● 2026-08-10 14:17:58
●NSns5.netnames.net2016-12-15 → 2026-08-10 · 2 obs
● 2026-08-10 14:17:58
●NSns6.netnames.net2016-12-15 → 2026-08-10 · 2 obs
● 2026-08-10 14:17:58
●MXrelay1.netnames.net2016-12-15 → 2026-08-10 · 2 obs
● 2026-08-10 14:17:58
●MXrelay2.netnames.net2016-12-15 → 2026-08-10 · 2 obs
● 2026-08-10 14:17:58
●A165.160.13.202026-03-02 → 2026-08-10 · 3 obs
● 2026-03-02 15:26:24
● 2026-08-10 14:17:58
●A165.160.15.202026-03-02 → 2026-08-10 · 3 obs
● 2026-03-02 15:26:24
● 2026-08-10 14:17:58
○A185.26.230.1292016-12-15 → 2017-09-16 · 4 obs
● 2017-09-16 00:28:54
○ 2026-03-02 15:26:24
○ 2026-08-10 14:17:58
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| ipfint.com | ns2.netnames.net, ns1.netnames.net, ns5.netnames.net, ns6.netnames.net | - |
✅ Authoritative Response
Server:156.154.130.100
NS records: ns2.netnames.net, ns1.netnames.net, ns5.netnames.net, ns6.netnames.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for ipfint.com (unsigned zone)
⏱️ Timing
Total: 615ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 165.160.13.20, 165.160.15.20 |
| NS | 4 | ns1.netnames.net, ns2.netnames.net... |
| MX | 2 | relay1.netnames.net (pri: 10), relay2.netnames.net (pri: 20) |
| TXT | 3 | MS=ms32315946, RO8GqJlFET3kVY3E07lwJinXCnxmIhGPjCxQf5Ww... |
| SOA | 1 | ns1.netnames.net hostmaster.cscdns.net |
Analysis
IP Addresses
ipfint.com has two IP addresses: 165.160.13.20 and 165.160.15.20
Additional host names — natixispayments.org, justplantforlife.com, bellphoneco.com and two others — share IP numbers with ipfint.com.
Name Servers
ipfint.com has four authoritative name servers: ns1.netnames.net, ns2.netnames.net, ns5.netnames.net and ns6.netnames.net.
The name servers of ipfint.com overlap at least partially with those of other domains — among them mcmexpogroup.com, cordiahealthcare.co.uk, movicol.org and two more.
These name servers commonly appear alongside the name servers ns7.netnames.net and ns8.netnames.net.
ns1.netnames.net and ns5.netnames.net both point to 156.154.130.100 and 2610:a1:1022::100; ns2.netnames.net and ns6.netnames.net both point to 156.154.131.100 and 2610:a1:1023::100 — all four hostnames (ns1.netnames.net, ns2.netnames.net, ns5.netnames.net and ns6.netnames.net) resolve to exactly two IP addresses.
ns1.netnames.net along with ns5.netnames.net each resolve to 2610:a1:1022::100 IP addresses.
ns1.netnames.net along with ns5.netnames.net each resolve to 156.154.130.100 IP addresses.
ns2.netnames.net along with ns6.netnames.net each resolve to 2610:a1:1023::100 IP addresses.
ns2.netnames.net along with ns6.netnames.net each resolve to 156.154.131.100 IP addresses.
Mail Servers
ipfint.com has two mail servers: relay1.netnames.net and relay2.netnames.net.
ipfint.com shares the same mail server setup as other domains, including barkleyvisa.it, sopra.in, scor-us.com and two others.
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.