ftcservices.com - dns.ninja
ftcservices.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=1784141192 | ||||||
Same first word
ftcservices.com |
Similar names
DNS History
9 records (8 active, 1 former)
โNSns1.netfirms.com2026-02-22 โ 2026-07-15 ยท 3 obs
โ 2026-02-22 13:37:00
โ 2026-07-15 19:08:46
โNSns1.yourhostingaccount.com2015-07-09 โ 2026-07-15 ยท 2 obs
โ 2026-07-15 19:08:46
โNSns2.netfirms.com2026-02-22 โ 2026-07-15 ยท 3 obs
โ 2026-02-22 13:37:00
โ 2026-07-15 19:08:46
โNSns2.yourhostingaccount.com2015-07-09 โ 2026-07-15 ยท 2 obs
โ 2026-07-15 19:08:46
โMXalt1.aspmx.l.google.com2015-07-09 โ 2026-07-15 ยท 2 obs
โ 2026-07-15 19:08:46
โMXalt2.aspmx.l.google.com2015-07-09 โ 2026-07-15 ยท 2 obs
โ 2026-07-15 19:08:46
โMXaspmx.l.google.com2015-07-09 โ 2026-07-15 ยท 2 obs
โ 2026-07-15 19:08:46
โA66.96.160.1352026-02-22 โ 2026-07-15 ยท 3 obs
โ 2026-02-22 13:37:00
โ 2026-07-15 19:08:46
โA68.109.232.1082015-07-09 โ 2019-01-07 ยท 4 obs
โ 2019-01-07 02:47:38
โ 2026-02-22 13:37:00
โ 2026-07-15 19:08:46
๐ DNS Trace
๐ Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, m.gtld-servers.net, c.gtld-servers.net, i.gtld-servers.net... | - |
| ftcservices.com | ns1.netfirms.com, ns2.netfirms.com | 4 records |
โ Authoritative Response
Server:162.159.25.208
NS records: ns1.netfirms.com, ns2.netfirms.com
๐ DNSSEC Status
โ ๏ธ Insecure (no DNSSEC)
No DS record for ftcservices.com (unsigned zone)
โฑ๏ธ Timing
Total: 233ms | Queries: -
๐ Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 66.96.160.135 |
| NS | 2 | ns2.yourhostingaccount.com, ns1.yourhostingaccount.com |
| MX | 3 | alt1.aspmx.l.google.com (pri: 10), aspmx.l.google.com (pri: 1)... |
| TXT | 4 | FfNarpeH, AXVR5JX88HHF66MRSPR63KHF6... |
| SOA | 1 | ns1.yourhostingaccount.com admin.yourhos |
๐ Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns1.netfirms.com, ns1.netfirms.com, ns2.netfirms.com...)
Analysis
IP Addresses
ftcservices.com directs to one IP number, which is 66.96.160.135.
Among the host names that share IP numbers with ftcservices.com are biplanedenver.com, cyphersystems.net, ns3.nadt.ca and two others.
Name Servers
The domain ftcservices.com is delegated to these four name servers: ns1.netfirms.com, ns2.netfirms.com, ns1.yourhostingaccount.com and ns2.yourhostingaccount.com.
ftcservices.com has at least partial name server overlap with other domains, such as californiacongressman.com, hola-mexico.com, nancydidion.com and two others.
ns1.mydomain.com, ns2.mydomain.com and ns1.dotster.com โ plus 7 other name servers โ are commonly paired with these name servers.
ns1.netfirms.com resolves to 162.159.24.252. ns2.netfirms.com resolves to 162.159.25.208. ns1.yourhostingaccount.com resolves to 65.254.254.102. ns2.yourhostingaccount.com resolves to 65.254.254.155. All four hosts carry exactly one IP address.
Mail Servers
ftcservices.com has three mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com.
ftcservices.com shares at least some of its mail servers with other domains โ for example unm.zone, lizardbuttekennelclub.org, ns500841.ns500795.ns500795.ns500795.ns500821.ns500795.ns500794.ns500795.ns500795.ns500790.ns500795.lustypartnersfinder.com and two more.
It is common to find these mail servers paired with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 more.
aspmx.l.google.com resolves to 192.179.18.26 and 2607:f8b0:4004:c2d::1a. alt1.aspmx.l.google.com resolves to 108.177.123.27 and 2800:3f0:4003:c0f::1b. alt2.aspmx.l.google.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1a. All three hostnames point to two IP numbers each.