translating.com - dns.ninja
translating.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 66.45.246.141🇺🇸 NJIIX-166.45.224.0/19 NJIIX.net 110B Meadowlands Pkwy Secaucus, NJ 07094 | ||||||
| NS | ns1.domainrecover.com ⭐ ⚠️ Not in parent delegation | ||||||
| A | 149.248.38.58🇺🇸 AS-VULTR149.248.32.0/20 Vultr Assigned Prefix | ||||||
| PTR | 149.248.38.58.vultrusercontent.com | ||||||
| NS | ns1.serverhome.com ⚠️ Not in zone NS records | ||||||
| A | 149.248.38.58🇺🇸 AS-VULTR149.248.32.0/20 Vultr Assigned Prefix | ||||||
| PTR | 149.248.38.58.vultrusercontent.com | ||||||
| NS | ns2.domainrecover.com ⚠️ Not in parent delegation | ||||||
| A | 199.247.16.62🇩🇪 AS-VULTR199.247.16.0/21 Vultr Assigned Prefix | ||||||
| PTR | 199.247.16.62.vultrusercontent.com | ||||||
| NS | ns2.serverhome.com ⚠️ Not in zone NS records | ||||||
| A | 199.247.16.62🇩🇪 AS-VULTR199.247.16.0/21 Vultr Assigned Prefix | ||||||
| PTR | 199.247.16.62.vultrusercontent.com | ||||||
| TXT | yGjyZf7SHD | ||||||
| SOA | ns1.domainrecover.comhostmaster@domainreover.com serial=1623031840 | ||||||
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=1785903524 | ||||||
Same first word
translating.me |
translating.cl |
translating.de |
translating.com.ua |
translating.kz |
translating.ru |
translating.co |
translating.ca |
translating.com |
Similar names
DNS History
17 records (5 active, 12 former)
●NSns1.domainrecover.com2026-02-21 → 2026-08-05 · 3 obs
● 2026-02-21 17:51:04
● 2026-08-05 04:47:06
●NSns1.serverhome.com2016-08-23 → 2026-08-05 · 3 obs
● 2016-08-23 16:41:30
● 2026-08-05 04:47:06
○NSns1.telenetcom.com2015-07-21 → 2016-05-01 · 4 obs
● 2016-05-01 15:47:42
○ 2016-05-16 04:10:48
○ 2026-08-05 04:47:06
●NSns2.domainrecover.com2026-02-21 → 2026-08-05 · 3 obs
● 2026-02-21 17:51:04
● 2026-08-05 04:47:06
●NSns2.serverhome.com2016-08-23 → 2026-08-05 · 3 obs
● 2016-08-23 16:41:30
● 2026-08-05 04:47:06
○NSns2.telenetcom.com2015-07-21 → 2016-05-01 · 4 obs
● 2016-05-01 15:47:42
○ 2016-05-16 04:10:48
○ 2026-08-05 04:47:06
○MXmx1.telenetcom.com2015-07-21 → 2016-05-01 · 4 obs
● 2016-05-01 15:47:42
○ 2016-05-16 04:10:48
○ 2026-08-05 04:47:06
○MXmx2.telenetcom.com2015-07-21 → 2016-05-01 · 4 obs
● 2016-05-01 15:47:42
○ 2016-05-16 04:10:48
○ 2026-08-05 04:47:06
○MXmxs1.domainrecover.com2016-06-05 → 2016-08-23 · 6 obs
● 2016-06-05 03:07:34
○ 2016-08-12 22:19:02
● 2016-08-23 16:41:30
○ 2016-11-03 19:41:46
○ 2026-08-05 04:47:06
○MXmxs1.telenetcom.com2016-11-03 → 2016-11-21 · 5 obs
● 2016-11-03 19:41:46
● 2016-11-21 12:14:48
○ 2026-02-21 17:51:04
○ 2026-08-05 04:47:06
○MXmxs2.domainrecover.com2016-06-05 → 2016-08-23 · 6 obs
● 2016-06-05 03:07:34
○ 2016-08-12 22:19:02
● 2016-08-23 16:41:30
○ 2016-11-03 19:41:46
○ 2026-08-05 04:47:06
○MXmxs2.telenetcom.com2016-11-03 → 2016-11-21 · 5 obs
● 2016-11-03 19:41:46
● 2016-11-21 12:14:48
○ 2026-02-21 17:51:04
○ 2026-08-05 04:47:06
○A209.50.247.1172016-11-03 → 2016-11-21 · 5 obs
● 2016-11-03 19:41:46
● 2016-11-21 12:14:48
○ 2026-02-21 17:51:04
○ 2026-08-05 04:47:06
●A66.45.246.1412026-02-21 → 2026-08-05 · 3 obs
● 2026-02-21 17:51:04
● 2026-08-05 04:47:06
○A66.45.246.1422016-05-16 → 2016-08-23 · 5 obs
● 2016-05-16 04:10:48
● 2016-08-23 16:41:30
○ 2016-11-03 19:41:46
○ 2026-08-05 04:47:06
○A67.209.228.1082015-07-21 → 2016-05-01 · 4 obs
● 2016-05-01 15:47:42
○ 2016-05-16 04:10:48
○ 2026-08-05 04:47:06
○CNAMEspres.serverhome.com2016-05-16 → 2016-08-23 · 4 obs
● 2016-08-23 16:41:30
○ 2016-11-03 19:41:46
○ 2026-08-05 04:47:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | m.gtld-servers.net, b.gtld-servers.net, e.gtld-servers.net, l.gtld-servers.net... | - |
| translating.com | ns1.serverhome.com, ns2.serverhome.com | 2 records |
✅ Authoritative Response
Server:199.247.16.62
NS records: ns1.serverhome.com, ns2.serverhome.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for translating.com (unsigned zone)
⏱️ Timing
Total: 251ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 66.45.246.141 |
| NS | 2 | NS2.DOMAINRECOVER.com, NS1.DOMAINRECOVER.com |
| TXT | 1 | yGjyZf7SHD |
| SOA | 1 | ns1.domainrecover.com hostmaster.domainr |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.serverhome.com, ns2.serverhome.com)
Analysis
IP Addresses
translating.com points to a single IP number: 66.45.246.141.
Additional host names — alvema.com, ortodont.com, heartspirit.com and two others — share IP numbers with translating.com.
Name Servers
translating.com has four authoritative name servers: ns1.domainrecover.com, ns2.domainrecover.com, ns1.serverhome.com and ns2.serverhome.com.
The name servers of translating.com overlap at least partially with those of other domains — among them biohk.com, pse2.com, playmotors.com and two more.
These name servers commonly appear alongside the name servers ns2.servering.com and ns.servering.com.
Each of the host names ns1.domainrecover.com, ns2.domainrecover.com, ns1.serverhome.com and ns2.serverhome.com has one IP address: ns1.domainrecover.com resolves to 149.248.38.58, ns2.domainrecover.com resolves to 199.247.16.62, ns1.serverhome.com resolves to 149.248.38.58 and ns2.serverhome.com resolves to 199.247.16.62.
These two host names — ns1.domainrecover.com and ns1.serverhome.com — each point to 149.248.38.58 IP addresses.
These two host names — ns2.domainrecover.com and ns2.serverhome.com — each point to 199.247.16.62 IP addresses.