inputlink.com - dns.ninja
inputlink.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 ⭐ | ||||||
| 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 | ||||||
| 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=1782545695 | ||||||
Same first word
inputlink.net |
inputlink.com |
DNS History
11 records (3 active, 8 former)
●NSns1.domainrecover.com2026-03-31 → 2026-06-27 · 3 obs
● 2026-03-31 14:55:22
● 2026-06-27 07:59:16
○NSns1.dsredirection.com2015-11-09 → 2016-04-24 · 4 obs
● 2016-04-24 06:39:20
○ 2016-12-31 07:09:58
○ 2026-06-27 07:59:16
●NSns2.domainrecover.com2026-03-31 → 2026-06-27 · 3 obs
● 2026-03-31 14:55:22
● 2026-06-27 07:59:16
○NSns2.dsredirection.com2015-11-09 → 2016-04-24 · 4 obs
● 2016-04-24 06:39:20
○ 2016-12-31 07:09:58
○ 2026-06-27 07:59:16
○MXmxs1.domainrecover.com2015-07-06 → 2019-12-31 · 4 obs
● 2019-12-31 04:13:02
○ 2026-03-31 14:55:22
○ 2026-06-27 07:59:16
○MXmxs2.domainrecover.com2015-07-06 → 2019-12-31 · 4 obs
● 2019-12-31 04:13:02
○ 2026-03-31 14:55:22
○ 2026-06-27 07:59:16
○A141.8.230.202015-07-06 → 2016-12-31 · 4 obs
● 2016-12-31 07:09:58
○ 2019-12-31 04:13:02
○ 2026-06-27 07:59:16
●A66.45.246.1412026-03-31 → 2026-06-27 · 3 obs
● 2026-03-31 14:55:22
● 2026-06-27 07:59:16
○CNAMEpres.serverhome.com2015-07-06 → 2016-12-31 · 4 obs
● 2016-12-31 07:09:58
○ 2019-12-31 04:13:02
○ 2026-06-27 07:59:16
○CNAMEsnews.serverhome.com2019-12-31 → 2019-12-31 · 4 obs
● 2019-12-31 04:13:02
○ 2026-03-31 14:55:22
○ 2026-06-27 07:59:16
○CNAMEthie5ku9.dsgeneration.com2015-11-09 → 2016-04-24 · 5 obs
● 2015-11-09 20:45:44
● 2016-04-24 06:39:20
○ 2016-12-31 07:09:58
○ 2026-06-27 07:59:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| inputlink.com | ns1.domainrecover.com, ns2.domainrecover.com | 2 records |
✅ Authoritative Response
Server:199.247.16.62
NS records: ns1.domainrecover.com, ns2.domainrecover.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for inputlink.com (unsigned zone)
⏱️ Timing
Total: 409ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 66.45.246.141 |
| NS | 2 | NS1.DOMAINRECOVER.com, NS2.DOMAINRECOVER.com |
| TXT | 1 | yGjyZf7SHD |
| SOA | 1 | ns1.domainrecover.com hostmaster.domainr |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.domainrecover.com, ns2.domainrecover.com)
Analysis
IP Addresses
inputlink.com resolves to just one IP address, 66.45.246.141.
Two other host names, along with givaid.com, planetazoo.com and domainfond.com, also share IP numbers with inputlink.com.
Name Servers
inputlink.com uses two name servers for its delegation: ns1.domainrecover.com and ns2.domainrecover.com.
inputlink.com shares its NS records with other domains, for example koalicja.com, msbook.com, huikeshoven.com and two others.
The name servers of inputlink.com overlap at least partially with those of other domains — among them incenia.com, nacor.com, 2t6.com and two more.
These name servers commonly co-occur with the name servers ns1.serverhome.com, ns2.serverhome.com, ns.servering.com and ns2.servering.com.
Both ns1.domainrecover.com and ns2.domainrecover.com have a single IP address each — ns1.domainrecover.com resolves to 149.248.38.58 while ns2.domainrecover.com resolves to 199.247.16.62.